Open giovannibaratta opened 9 months ago
HI @giovannibaratta I tried to reproduce the issue using the provided terraform config but unable to reproduce it. Can you provide the alb provider and controller version which you are using? Also add if you are performing any manual operations on pool from UI side
The terraform provider version is 22.1.5
The controller version is 30.1.1-9415
provider "avi" {
...
avi_version = "30.1.1"
}
All the AVI resources are provisioned using Terraform except for the Cloud configuration. The behavior is observed is subsequent runs (terraform plan/apply) without the need of open the UI.
@giovannibaratta Thanks for raising this issue; I am able to reproduce the issue. In the release of 22.1.5, we fixed the issue to track the UI side changes. While applying the Terraform plan, earlier it was not there; that's why it is showing diff, and some internal fields are part of the resource schema; those fields should not come. I will update here once I fix the issue.
Thanks
As this is really annoying, is there an ETA for the fix? Running provider 22.1.5
with controller 22.1.5 2p3 build 9093
.
We're still desperately waiting for this to be fixed. Can you @Rohan-sss1 provide an ETA?
Describe the bug
When creating a resource of type
avi_pool
, leaving the attributediscovered_networks
inservers
will produce a diff in subsequent plan/apply.Reproduction steps
Result in this terraform diff
Expected behavior
Terraform should not generate any difference during subsequent plan/apply
Additional context
From my understanding
discovered_networks
should be an internal-use attribute and it should not even be proposed as an editable attribute in terraform. In this case, leaving the attribute unset will produce the diff posted above.