-
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
Validate BigQuery naming requirements before apply #12284
Validate BigQuery naming requirements before apply #12284
Comments
Here is an example of a workflow that the lack of validation "enables":
|
This isn't something the google terraform provider has native support for, I'd recommend defining your validation rules on an input variable instead: https://www.terraform.io/language/values/variables#custom-validation-rules. Or if you want to go even further than that, there is a terraform provider for jsonschema validation - which also does a good job of creating custom enforced rules: https://registry.terraform.io/providers/JeffAshton/jsonschema/latest/docs |
I don't know about the validation rules. Is there a document detailing everything? Otherwise, I'd have to go the trial and error route which is what we already are doing with all the failures in CI. I'd think the provider is a better chokepoint to implement this kind of validation. |
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. |
Description
Plan shows resources will be created but then it fails during apply.
It'd be more productive if Terraform would validate that the names satisfy the requirements before applying.
New or Affected Resource(s)
b/308248587
The text was updated successfully, but these errors were encountered: