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
I am using Terraform 0.12.29 and ibm cloud provider plugin v1.11.0. I am able to create vsi using version which mentioned, but there is issue after creation when I rerun again it is destroying existing vsi and recreating, even if there is no change in the vm configuration. terraform command output what I can see is "- os_reference_code = "REDHAT_7_64" -> null # forces replacement " though I have not use os_reference_code in my code, I have used image_id in my code. It is weird issue I am seeing, appreciate any help
Hi there,
I am using Terraform 0.12.29 and ibm cloud provider plugin v1.11.0. I am able to create vsi using version which mentioned, but there is issue after creation when I rerun again it is destroying existing vsi and recreating, even if there is no change in the vm configuration. terraform command output what I can see is "- os_reference_code = "REDHAT_7_64" -> null # forces replacement " though I have not use os_reference_code in my code, I have used image_id in my code. It is weird issue I am seeing, appreciate any help
Terraform Version
Terraform v0.12.29
Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
Expected Behavior
It shouldn't recreate the resource since there is no change in the configuration when we re run next attempt
Actual Behavior
It is destroying existing resource and creating new one even though there is no change in the configuration
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform init
terraform plan
terraform apply
After successful creation of resource just rerunning it again
terraform init
terraform plan - tells it is going to add 1 resource and destroy 1 resource even though there is no change in the configuration
terraform apply - It destroys the existing resource and create new one even though there is no change in the configuration
Important Factoids
References
The text was updated successfully, but these errors were encountered: