Skip to content

Maintenance: simplify script to update layer ARN #3890

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.

Sign up for GitHub

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

Jump to bottom
Open
1 of 2 tasks
dreamorosi opened this issue May 5, 2025 · 0 comments
Open
1 of 2 tasks

Maintenance: simplify script to update layer ARN #3890

dreamorosi opened this issue May 5, 2025 · 0 comments
Labels
automation This item relates to automation confirmed The scope is clear, ready for implementation internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)

Comments

@dreamorosi
Copy link
Contributor

Summary

The current script at .github/scripts/update_layer_arn.sh was built to handle different ARNs and different version numbers across regions.

It served us well, but now that we have settled on always keeping version numbers aligned, we don't need all the complexity included in it, and instead we can just take a new Lambda layer version as input and update the documentation accordingly.

We should update the workflow to do exactly this.

Why is this needed?

So that we can keep things simple and remove unneeded code.

Which area does this relate to?

Automation

Solution

No response

Acknowledgment

Future readers

Please react with 👍 and your use case to help us understand customer demand.
@dreamorosi dreamorosi added automation This item relates to automation internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) labels May 5, 2025
@dreamorosi dreamorosi added the confirmed The scope is clear, ready for implementation label May 5, 2025
@dreamorosi dreamorosi moved this from Triage to Backlog in Powertools for AWS Lambda (TypeScript) May 5, 2025
@dreamorosi dreamorosi mentioned this issue May 5, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
automation This item relates to automation confirmed The scope is clear, ready for implementation internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Projects
Powertools for AWS Lambda (TypeScript)
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dreamorosi