Skip to content
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

Composer zone field in config.node_config shouldn't be required #10324

Closed
kubasieron opened this issue Oct 14, 2021 · 2 comments · Fixed by GoogleCloudPlatform/magic-modules#5320, hashicorp/terraform-provider-google-beta#3745 or #10353
Assignees
Labels

Comments

@kubasieron
Copy link

kubasieron commented Oct 14, 2021

Community Note

  • 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

Affected Resource(s)

  • google_composer_environment

Expected Behavior

Zone field in composer resource config.node_config is required, but instead should be optional. It is inconsistent with composer API and blocks creating composer v2 environments with non-empty node_config.

@kubasieron kubasieron added the bug label Oct 14, 2021
@kubasieron
Copy link
Author

I wish to work on that item

@github-actions
Copy link

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.