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
A disk should have been added (it was) and the state should have been updated with the last_request return (resource_ids and status) but it wasn't. When no changes are made to the input, and the resources haven't drifted, no state drift or resource changes should be required.
Actual Behavior
Terraform advised "Note: Objects have changed outside of Terraform" and indicates the vra_deployment resource has changed in both the last_request and resources attributes and shows a diff that is not representative of the actions that will be takes (it shows a complete removal of the virtual machine
Unless you have made equivalent changes to your configuration, or ignored the relevant attributes using ignore_changes, the following plan may include actions to undo or respond to these changes.
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
The text was updated successfully, but these errors were encountered:
This issue seems to be happening due to the sync_status field from what I can see. I get this same issue when changing ANY field on a day 2 action. It seems the field is updated after the deployment is created and the tfstate is written - possibly a job running that does a sync and updates this field.
On successful creation of the deployment, my tfstate shows the following:
"sync_status": ""
When I update any field on my terraform resource e.g. memory or adding disks and run a plan, the only value actually changing is:
+ sync_status = "SUCCESS"
It seems this field is only populated when a day 2 action is triggered where it possibly runs a sync.
vRA Version
8.7.0.21169 (19508505)
Terraform Version
v1.3.2
vRA Terraform Provider Version
0.5.2
Affected Resource(s)
vra_deployment
Terraform Configuration Files
tfvar file is initially set with :
but then after the build, update it:
Expected Behavior
A disk should have been added (it was) and the state should have been updated with the last_request return (resource_ids and status) but it wasn't. When no changes are made to the input, and the resources haven't drifted, no state drift or resource changes should be required.
Actual Behavior
Terraform advised "Note: Objects have changed outside of Terraform" and indicates the vra_deployment resource has changed in both the last_request and resources attributes and shows a diff that is not representative of the actions that will be takes (it shows a complete removal of the virtual machine
Unless you have made equivalent changes to your configuration, or ignored the relevant attributes using ignore_changes, the following plan may include actions to undo or respond to these changes.
Steps to Reproduce
Debug Output
N/A
Panic Output
N/A
Important Factoids
N/A
References
N/A
Community Note
The text was updated successfully, but these errors were encountered: