You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
If an issue is assigned to the "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 to "hashibot", a community member has claimed the issue already.
Terraform Version
Terraform v0.11.11
Affected Resource(s)
google_composer_environment
Expected Behavior
It should have created the composer cluster.
Actual Behavior
* module.dataplatform_common.google_composer_environment.<resource name>: 1 error(s) occurred:
* google_composer_environment.<resource name>: A zone must be specified
When both machine_type and zone options are not included we get the following error:
Error: Error applying plan:
1 error(s) occurred:
* module.dataplatform_common.google_composer_environment.<resource name>: 1 error(s) occurred:
* google_composer_environment.<resource name>: The zonal field for resource machineTypes cannot be empty.
When a zone is specified and the machine_type gets omitted the plan gets applied without any issues.
We think that this is a new requirement by Google since even when we try to create a composer cluster via gcloud we get the following:
$ gcloud composer environments create <project> --location=us-central1 --machine-type=n1-standard-1
ERROR: (gcloud.composer.environments.create) value for field [zone] in collection [compute.machineTypes] is required but was not provided
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!
ghost
locked and limited conversation to collaborators
Mar 4, 2019
Community Note
Terraform Version
Terraform v0.11.11
Affected Resource(s)
Expected Behavior
It should have created the composer cluster.
Actual Behavior
Steps to Reproduce
terraform apply
According to the documentation for the google_composer_environment resource, zone and machine_type are optional fields to be defined in a tf manifest (https://www.terraform.io/docs/providers/google/r/composer_environment.html#node_config). When we specify a machine_type in our manifest we get the error included above.
When both machine_type and zone options are not included we get the following error:
When a zone is specified and the machine_type gets omitted the plan gets applied without any issues.
We think that this is a new requirement by Google since even when we try to create a composer cluster via gcloud we get the following:
This seems something that needs to be updated on your end both on the docs and source code, since even looking at the source code for the composer resource, zone is defined as optional: https://github.com/terraform-providers/terraform-provider-google/blob/97347e5de57c7199f963599acc50f5df9391288b/google/resource_composer_environment.go#L92
The text was updated successfully, but these errors were encountered: