-
Notifications
You must be signed in to change notification settings - Fork 696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The folder operation violates display name uniqueness within the parent. #33
Comments
Hi @sbadakhc can you please share the output of |
Hi @rjerrems. Here is the terraform output from the 1-org directory.
I have made no code modifications and this is a vanilla platform that I can continue to bounce until I get this working. I want to achieve a clean run be before I begin customising things. Thanks, |
@rjerrems - I just tried to destroy the resources and I'm seeing the error below. It seems I am stick on one hand from completing the 'apply' and on the other from executing a 'destroy'. Let me know if I can provide more information. Thanks Sal.
|
Hi @sbadakhc , How did you get this uniqueness error sorted. I am trying example foundation for the first time and getting the exact same error. Appreciate if you could advise. Thanks. |
Hi,
I'm running terraform apply in 1-org dir. I can see that folders are created but I'm getting uniqueness error. Under my org I have successfully provisioned a common /logs /monitoring /networking folders and they appear to be populated correctly. Is the idempotency breaking here? If those folders exist I guess the apply should run without errors? Possibly related to:
hashicorp/terraform-provider-google#1903
The text was updated successfully, but these errors were encountered: