Skip to content

Maintenance(layer): add canary tests to layer deployment steps #1571

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
Closed
1 of 2 tasks
am29d opened this issue Jul 3, 2023 · 3 comments
Closed
1 of 2 tasks

Maintenance(layer): add canary tests to layer deployment steps #1571

am29d opened this issue Jul 3, 2023 · 3 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.) layers Items related to the Lambda Layers pipeline

Comments

@am29d
Copy link
Contributor

am29d commented Jul 3, 2023

Summary

Similar to the python deployment pipeline we need a canary deployment for layers in beta and prod env, so we can make sure that the layer we release can be imported attached to a function. This is not an e2e test for the layer, but for the release process, because we might get the configuration wrong by passing invalid version to the workflow step. See #1569.

Why is this needed?

To prevent misconfiguration of the layer packaging during release.

Which area does this relate to?

No response

Solution

No response

Acknowledgment

Future readers

Please react with 👍 and your use case to help us understand customer demand.
@am29d am29d added triage This item has not been triaged by a maintainer, please wait internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) labels Jul 3, 2023
@am29d am29d added automation This item relates to automation confirmed The scope is clear, ready for implementation layers Items related to the Lambda Layers pipeline and removed triage This item has not been triaged by a maintainer, please wait labels Jul 3, 2023
@dreamorosi
Copy link
Contributor

dreamorosi commented Jul 3, 2023 •
edited
Loading

Possibly a duplicate of #1355, if yes please close this one & let's use that one as main.

@am29d am29d closed this as not planned Won't fix, can't repro, duplicate, stale Jul 3, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Jul 3, 2023

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

@am29d
Copy link
Contributor Author

am29d commented Jul 3, 2023

Yep, I filtered by area/layer and did not find any thing. Thanks.

@dreamorosi dreamorosi moved this from Coming soon to Closed in Powertools for AWS Lambda (TypeScript) Jul 3, 2023
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.) layers Items related to the Lambda Layers pipeline
Projects
Powertools for AWS Lambda (TypeScript)
Status: Closed
Milestone
No milestone
Development

No branches or pull requests
2 participants
@am29d @dreamorosi