-
Notifications
You must be signed in to change notification settings - Fork 33
terraform apply always results in change despite not change to .tf #56
Comments
Same issue here. A |
In my testing I think this issue results in the following outcomes. Terraform has no knowledge of scaled-out VMs. Or perhaps this is a different issue? Create deployment = success |
@t-settle the original issue in this bug has been fixed. The plan will not show any diff if .tf file has no change. The scale out issue is reproducible. It is due to the vRA API limitation. Please open another bug for that for easy tracking. Thanks, |
vRA 7.x version
7.6
Terraform version
Terraform v0.12.18
terraform-provider-vra7 plugin version
Describe the bug
After upgrading to vra7 provider v1.0.0, I noticed executing terraform apply multiple times in a row results in a change, when nothing has been changed.
To Reproduce
provider "vra7" {
tenant = "acme"
host = "https://xxxx.xxxx.com"
insecure = "true"
}
resource "vra7_deployment" "myDeployment" {
count = 1
catalog_item_name = "bp_acme_develop"
businessgroup_name = "bizgroup1"
description = "Test Terraform deployment"
reasons = "Testing the vRA 7 Terraform plugin"
resource_configuration {
component_name = "vm"
cluster = 2
configuration = {}
}
}
Run "terraform apply"
get "Resources: 1 added, 0 changed, 0 destroyed."
Run "terraform apply" again
get "Resources: 0 added, 1 changed, 0 destroyed."
where it Null's out all the resources and then reapplies them all exactly the same.
Expected behavior
"Resources: 0 added, 0 changed, 0 destroyed."
on subsequent "terraform apply" with no change to the .tf file
Screenshots
If applicable, add screenshots to help explain your problem.
Logs
Attach logs to help debug the issue
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: