Add lastConnectivityTime to volatile fields list#1062
Merged
ms-henglu merged 2 commits intoAzure:mainfrom Mar 5, 2026
Merged
Conversation
This fixes an issue where the provider produces an inconsistent result after apply because the lastConnectivityTime field (returned by Azure HybridContainerService connected cluster resources) changes between the create/update and the subsequent read. Fixes Azure#1061
…ityTime-to-volatile-fields
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Add
lastConnectivityTimeto the volatile fields list to preventProvider produced inconsistent result after applyerrors.Fix
The
lastConnectivityTimefield is returned by Azure HybridContainerService connected cluster resources and changes frequently (e.g., between the create/update call and the subsequent read). Since this field is not in thevolatileFieldList(), it gets included in the default output, causing Terraform to detect an inconsistency between the planned and actual values.This PR adds
lastConnectivityTimeto the volatile fields list alongside other time-related fields that are already excluded.Fixes #1061