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.14
+ provider.google v2.8.0
Affected Resource(s)
google_bigtable_instance
We have previously been able to use the same module for prod and development and templating in values for number of nodes, type, etc, that differs between environments. As of #2401 / GoogleCloudPlatform/magic-modules#679, we can no longer reuse templates in this way, so it is a breaking change for us (since we can't have fields optionally unset). I'd prefer being able to set num_nodes to 1 for development instances only.
You're correct that this was a breaking change- it was made as part of a major release, 2.0.0. num_nodes not being able to be set for DEVELOPMENT instances improves the validation of the resource, so I'm not sure it's a change I'd like to revert either. Additionally, this is solved entirely by using Terraform 0.12 instead of Terraform 0.11, where conditionally setting fields is possible.
Setting instance_type to Required would be another breaking change, so that's not really feasible.
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
Oct 6, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Terraform Version
Affected Resource(s)
We have previously been able to use the same module for prod and development and templating in values for number of nodes, type, etc, that differs between environments. As of #2401 / GoogleCloudPlatform/magic-modules#679, we can no longer reuse templates in this way, so it is a breaking change for us (since we can't have fields optionally unset). I'd prefer being able to set num_nodes to 1 for development instances only.
Alternatively, make
instance_type
required to avoid the scenario motivating GoogleCloudPlatform/magic-modules#679The text was updated successfully, but these errors were encountered: