Properly force a new resource whenenver the cert is near expiry #1440
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.
Affected resources:
The previous approach would leave some computed values out of sync
whenever the certificate determined to be expired. This was
because the approach attempted to leverage a combination of schema
CustomizeDiff
,and
Update
functions, rather than taking advantage of the ability tomark the resource as requiring replacement within the
CustomizeDiff
function itself.
Community Note
Closes #835
Release note for CHANGELOG:
Output from acceptance testing: