-
Notifications
You must be signed in to change notification settings - Fork 153
feat(ci): Add advanced automation #3438
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
Conversation
|
No related issues found. Please ensure there is an open issue related to this change to avoid significant delays or closure. |
No acknowledgement section found. Please make sure you used the template to open a PR and didn't remove the acknowledgment section. Check the template here: https://github.com/aws-powertools/powertools-lambda-typescript/blob/develop/.github/PULL_REQUEST_TEMPLATE.md#acknowledgment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the update - I just want to make sure we're using the CDK version from the project, so we can be sure that it'll work since we're already using it in other workflows.
Other than that, assuming we have no way to test this or it has already been tested elsewhere - is there a way to make the update_ssm
one part of the release workflow?
Or should we keep it as a manual step? If yes, why?
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still would have preferred to use the CDK version in the project rather than pinning it, like we discussed, but I also want to move forward and close this PR.
If the OpenSSF Scorecard complains I'll make another commit do it.
Summary
Changes
This PR adds the ability to bootstrap new regions and create SSM parameters to alias Lambda Layer ARNs.
Issue number: #3200, #3439
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.