Terraform Resource Attribute Set to Null on Second Apply Without Changes #35351
Labels
bug
new
new issue not yet triaged
waiting-response
An issue/pull request is waiting for a response from the community
Terraform Version
Terraform Configuration Files
Debug Output
Expected Behavior
Terraform should detect no changes and confirm the infrastructure is up-to-date without setting any resource attributes to null.
To elaborate, when running terraform apply a second time without making any changes to the resources, Terraform should recognize that the current state matches the desired configuration as defined in the .tf files. It should not alter the existing resources or their attributes, and it should certainly not set any previously defined attributes (e.g., name = "John Doe") to null.
Actual Behavior
When running terraform apply a second time without making any changes to the Terraform configuration, the expected behavior is for Terraform to recognize that no changes are required and confirm that the infrastructure is already up-to-date. However, the actual behavior observed is that a specific resource attribute, name, is being unexpectedly set to null. This indicates a discrepancy between the Terraform state and the actual configuration or the infrastructure, resulting in unintended modifications to the resource state.
Steps to Reproduce
Additional Context
No response
References
github issue not yet created
The text was updated successfully, but these errors were encountered: