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
Now, for external name configuration, we choose the longest one (in the first order) and use this string for constructing Terraform ID.
In the previous days, we discuss that using the shortest one (in the last order). So we tried to use the NameAsIdentifier configuration choice.
During this test we observed that the Terraform ID was overridden after Terraform call.
In first loop, we construct the ID by using only external name: example and write to the terraform.tfstate. After Terraform calls, Terraform overrides the ID in the terraform.tfstate and sets to the longest one: projects/official-provider-testing/regions/us-central/resourcePolicies/example.
So, I opened this issue to discuss the possible impacts of this behavior.
The text was updated successfully, but these errors were encountered:
In provider-gcp for many resources there are more than one possible import statements:
Now, for external name configuration, we choose the longest one (in the first order) and use this string for constructing Terraform ID.
In the previous days, we discuss that using the shortest one (in the last order). So we tried to use the NameAsIdentifier configuration choice.
During this test we observed that the Terraform ID was overridden after Terraform call.
In first loop, we construct the ID by using only external name:
example
and write to theterraform.tfstate
. After Terraform calls, Terraform overrides the ID in theterraform.tfstate
and sets to the longest one:projects/official-provider-testing/regions/us-central/resourcePolicies/example
.So, I opened this issue to discuss the possible impacts of this behavior.
The text was updated successfully, but these errors were encountered: