-
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
Service Account error message not descriptive #671
Comments
So the actual solution to this that I think we should do is to provide a
The error message that's actually useful is hanging out in the Compare that to a similar error struct returned from the compute API:
I'll go ahead and add the |
Fixed in #793 |
Signed-off-by: Modular Magician <[email protected]>
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! |
Version: 0.10.2
Resources:
google_service_account
If the
account_id
property of agoogle_service_account
is invalid, the error message returned by Terraform is generic and doesn't surface the helpful message returned by the API. For example, anaccount_id
> 30 characters returns this message in Terraform:Error creating service account: googleapi: Error 400: Request contains an invalid argument., badRequest
The message returned by the API is helpful, but buried by Terraform:
Service account name must be between 6 and 30 characters (inclusive), must begin with a lowercase letter, and consist of alphanumeric characters that can be separated by hyphens.
Passing through the detailed error message from the API is the expected behavior.
Thanks!
The text was updated successfully, but these errors were encountered: