Skip to content

Maintenance: Deploy new Lambda Layers in existing Layer account #1328

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
2 tasks done
heitorlessa opened this issue Jul 20, 2022 · 1 comment
Closed
2 tasks done

Maintenance: Deploy new Lambda Layers in existing Layer account #1328

heitorlessa opened this issue Jul 20, 2022 · 1 comment
Assignees
Labels
internal Maintenance changes

Comments

@heitorlessa
Copy link
Contributor

Technical debt

We've migrated from Lambda Layers internal pipeline to GitHub Actions and created new accounts.

Why is this needed?

Organizations that added our account in their org allow list will have trouble in adopting the new Layer.

Which area does this relate to?

Automation

Solution

No response

Acknowledgment

@heitorlessa heitorlessa added triage Pending triage from maintainers internal Maintenance changes labels Jul 20, 2022
@heitorlessa heitorlessa removed the triage Pending triage from maintainers label Jul 20, 2022
@heitorlessa heitorlessa self-assigned this Jul 20, 2022
@github-actions github-actions bot added the pending-release Fix or implementation already in dev waiting to be released label Jul 20, 2022
@github-actions
Copy link
Contributor

This is now released under 1.26.6 version!

@github-actions github-actions bot removed the pending-release Fix or implementation already in dev waiting to be released label Jul 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal Maintenance changes
Projects
None yet
Development

No branches or pull requests

1 participant