Skip to content

chore(layers): add compatible architecture field #3544

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

Merged
merged 1 commit into from
Jan 29, 2025

Conversation

dreamorosi
Copy link
Contributor

Summary

Changes

Please provide a summary of what's being changed

This PR adds back the compatibleArchitectures field to our Lambda layers since all the regions we support today also support the field in their API.

Please add the issue number below, if no issue is present the PR might get blocked and not be reviewed

Issue number: closes #1400


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.

@dreamorosi dreamorosi self-assigned this Jan 29, 2025
@dreamorosi dreamorosi requested a review from a team January 29, 2025 16:57
@dreamorosi dreamorosi requested a review from a team as a code owner January 29, 2025 16:57
@boring-cyborg boring-cyborg bot added the layers Items related to the Lambda Layers pipeline label Jan 29, 2025
@pull-request-size pull-request-size bot added the size/XS PR between 0-9 LOC label Jan 29, 2025
@dreamorosi dreamorosi merged commit 4dd17cc into main Jan 29, 2025
44 checks passed
@dreamorosi dreamorosi deleted the chore/add_compatible_arch_layers branch January 29, 2025 17:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
layers Items related to the Lambda Layers pipeline size/XS PR between 0-9 LOC
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Maintenance: compatibleArchitectures field not available in all AWS Regions
2 participants