Skip to content
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

feat: Make compatible_runtimes optional, added sam metadata control #493

Merged
merged 8 commits into from
Oct 27, 2023

Conversation

ajschmidt8
Copy link
Contributor

Description

This PR makes the compatible_runtimes argument for the aws_lambda_layer_version resource optional.

Motivation and Context

Currently, the compatible_runtimes value is inferred from var.compatible_runtimes and var.runtime.

If neither of these values is set, the module throws an error.

I'm trying to use this module to publish a Lambda layer that doesn't depend on any particular runtime (it's just a plain-text configuration file).

Therefore, I'd expect that I'd be able to publish this layer without having to specify a runtime.

The official aws_lambda_layer_version resource docs mention that this argument is optional (see here), so I'd expect that it would be optional in this module as well.

Breaking Changes

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

@ajschmidt8 ajschmidt8 changed the title Make compatible_runtimes optional fix: make compatible_runtimes optional Aug 5, 2023
@ajschmidt8 ajschmidt8 changed the title fix: make compatible_runtimes optional fix: Make compatible_runtimes optional Aug 5, 2023
@ajschmidt8
Copy link
Contributor Author

@antonbabenko, can you take a look at this when you have a moment?

@github-actions
Copy link

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

@github-actions github-actions bot added the stale label Sep 16, 2023
@ajschmidt8
Copy link
Contributor Author

this is not stale.

@antonbabenko, can you check on this PR soon?

@github-actions github-actions bot removed the stale label Sep 17, 2023
@github-actions
Copy link

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

@github-actions github-actions bot added the stale label Oct 18, 2023
@ajschmidt8
Copy link
Contributor Author

@antonbabenko, can you check on this PR?

It addresses a legitimate bug.

@github-actions github-actions bot removed the stale label Oct 19, 2023
Copy link
Member

@antonbabenko antonbabenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! Thank you!

@antonbabenko antonbabenko changed the title fix: Make compatible_runtimes optional feat: Make compatible_runtimes optional, added sam metadata control Oct 27, 2023
@antonbabenko antonbabenko merged commit 180da4c into terraform-aws-modules:master Oct 27, 2023
27 checks passed
antonbabenko pushed a commit that referenced this pull request Oct 27, 2023
## [6.2.0](v6.1.0...v6.2.0) (2023-10-27)

### Features

* Make `compatible_runtimes` optional, added sam metadata control ([#493](#493)) ([180da4c](180da4c))
@antonbabenko
Copy link
Member

This PR is included in version 6.2.0 🎉

@ajschmidt8 ajschmidt8 deleted the fix-runtimes branch October 27, 2023 18:11
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants