fix: Avoid phantom resource changes in the plan #141
Merged
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.
what
*_ttl
params when custom cache policy is specified (TTLs included in the policy take precedence)TLSv1
minimum viewer policy for alias-less distributionwhy
Certain parameter combinations may lead to phantom changes in the plan. This PR aligns some arguments with AWS's default values that aren't explicitly stated in the documentation.
No matter how many times you apply the above, the plan always produces the following (the
min_ttl
does not show up, as it's set to0
by default):When a local module is referenced (
source = "../../"
), then the subsequent apply works as expected:No changes. Your infrastructure matches the configuration.
references