feat: Added the skip_destroy argument for functions #600
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
catrielg
changed the title
antonbabenko
changed the title
antonbabenko
approved these changes
Aug 23, 2024
antonbabenko
pushed a commit
that referenced
this pull request
Aug 23, 2024
## [7.8.0](v7.7.1...v7.8.0) (2024-08-23) ### Features * Added the skip_destroy argument for functions ([#600](#600)) ([36c6109](36c6109))
|
This PR is included in version 7.8.0 🎉 |
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Added the "skip_destroy" argument for the "function" resource.
More info from the AWS Provider Doc:
(Optional) Set to true if you do not wish the function to be deleted at destroy time, and instead just remove the function from the Terraform state.
Motivation and Context
Particularly useful for Lambda@Edge that cannot be destroyed if they are still associated with a CloudFront Distribution.