azurerm_key_vault_secret
: fix empty check for expiration in CustomizeDiff
#28920
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.
Community Note
Description
If the expiraion is dynamic value, it will always be empty in plan stage, This PR is to fix this issue in CustomizeDiff.
Testing
Because this is for a forceNew logic and currently AccTest cannot cover the case. So I only add a test to update the expiration field.
Change Log
Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.
azurerm_key_vault_secret
- fix CosmizeDiff of expiration_date [azurerm_key_vault_secret
forces replacement if expiration_date is not known until apply #28914]This is a (please select all that apply):
Related Issue(s)
Fixes #28914