Skip to content

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

Closed
@heitorlessa

Description

@heitorlessa

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

Metadata

Metadata

Assignees

Labels

internalMaintenance changes

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions