You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the value of a protected parameter is changed, an apply should update the protected parameter value and not change the value of the other parameters.
Actual Behaviour
An apply shows only the protected parameter being changed. However, the other parameters are wiped from state. A subsequent plan shows a change adding the parameters back in.
Steps to Reproduce
Deploy an azurerm_virtual_machine_run_command with protected and unprotected parameters.
Update a protected parameter value and apply the change.
Run a subsequent plan and notice that the unprotected parameters are being added again due to being previously being removed from state following the unrelated protected parameter update.
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Is there an existing issue for this?
Community Note
Terraform Version
1.7.4
AzureRM Provider Version
3.94
Affected Resource(s)/Data Source(s)
azurerm_virtual_machine_run_command
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
When the value of a protected parameter is changed, an apply should update the protected parameter value and not change the value of the other parameters.
Actual Behaviour
An apply shows only the protected parameter being changed. However, the other parameters are wiped from state. A subsequent plan shows a change adding the parameters back in.
Steps to Reproduce
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: