-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 lookup Cloud Build service account with data source. #8326
Cannot lookup Cloud Build service account with data source. #8326
Comments
/cc @rileykarson |
What an unusual restriction, given that it should just work using the FQN method! Assigning you since you've already got a PR out. I think https://registry.terraform.io/providers/hashicorp/google/latest/docs/data-sources/service_account#account_id will need to be updated as well to state that an email can be supplied. |
@rileykarson done in the PR |
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 👉 hashibot-feedback@hashicorp.com. 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
Affected Resource(s)
Terraform Configuration Files
Error Output
Expected Behavior
The data source should be able to lookup service accounts by email account_id. In fact, the helper that the data source uses,
serviceAccountFQN
, correctly handles this case. However, the provider has a validation on theaccount_id
that might be unnecessarily restrictive.Actual Behavior
Error above.
Steps to Reproduce
terraform apply
The text was updated successfully, but these errors were encountered: