-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Cannot create VPC Service Control perimeter using end-user credentials #6401
Comments
The user/sa should be an org level user for this resource. Can you try setting |
Hi @venkykuberan, I confirm I have this role on the organization level (hence why I can create it via gcloud command with no problems). |
@nauris-sadovskis API isn't allowing to use the regular user creds to create the resource outside of gcloud. I wonder if your user can impersonate to a SA and create the resource. You can look into this doc. Since its an API limitation i am closing this issue |
Thanks @venkykuberan, I have stumbled upon the following Medium article which does impersonation via Terraform: |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
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
Terraform v0.12.12
Affected Resource(s)
Terraform Configuration Files
Debug Output
https://gist.github.com/nauris-sadovskis/9f815a53cc4c9066b4416301e785b59b
Panic Output
N/A
Expected Behavior
The change should have been applied using end-user credentials. Following
gcloud
command works with no issues with end-user credentials:Actual Behavior
Steps to Reproduce
terraform apply
Important Factoids
Yes, I'm authenticating as a user and for all other terraform resources it works fine. I'm aware that best practice is to use service accounts, but for the auditing/security/criticality of the resource, it's being run using end-user credentials.
References
N/A
The text was updated successfully, but these errors were encountered: