Closed AlexandreAlvesL closed 2 years ago
@AlexandreAlvesL can you provide the steps to repro the issue? Did you bring the resource into state before you apply? For me it seems to be fine through apply and re-apply.
@edwardmedia did another try via a new project and also by clearing the state file in the existing project and it works as expected. most likely I provisioned via local code and then used it as part of the pipeline without clearing the configuration first. feel free to close this.
@AlexandreAlvesL glad you found the problem. Closing the issue then
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
v1.2.3 and v1.2.4
Affected Resource(s)
google_iam_workload_identity_pool
Terraform Configuration Files
Debug Output
(https://gist.github.com/AlexandreAlvesL/62ca81b51b6e6e5b2505cd67ea6b0b62)
Panic Output
Expected Behavior
It should have detected a existing resource already exists and nothing needs to be done.
Actual Behavior
A resource already exists and it crashes.
Steps to Reproduce
use the google_iam_workload_identity_pool and run it twice. First time to create the resouce, second time it will crash
terraform apply
Important Factoids
References
0000