feat: Ignore last_modified on aws_lambda_function #624
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
Signed-off-by: Edgar Castillo <edgar.castillo@gametime.co>
edgar-castle
changed the title
|
anddd, I PR'd this to the wrong repo, apologies! |
|
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
Adds the lifecycle ignore rule to the lambda function. Without this, it will prompt to re-deploy the lambda function anytime a plan/apply is performed (even without a change to the underlying src files). The behavior now is that it'll only trigger a re-deploy if the src code or the module call is changed.
Breaking Changes
N/A nothing is using this yet. Will be the first addition to the new release.
How Has This Been Tested?
I verified this locally, was able to do multiple plan/applies on a project without it wanting to update the lambda resource.