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

handle case where bigtable development instances have one node #1704

Conversation

modular-magician
Copy link
Collaborator

The API still doesn't permit setting the node count for development instances, but if we send it as empty it might return 0 or 1 back. Unfortunately, customizediff can't tell that the field isn't set in the config if it is set in state (regardless of whether it's set to computed), so we have to have it allow 1 as a value for num_nodes even though it'll fail at apply-time.

Fixes hashicorp/terraform-provider-google#5492.

Release Note Template for Downstream PRs (will be copied)

bigtable: fixed diff for DEVELOPMENT instances that are returned from the API with one node

Derived from GoogleCloudPlatform/magic-modules#3057

…corp#3057)

Signed-off-by: Modular Magician <magic-modules@google.com>
@ghost ghost added the size/xs label Jan 31, 2020
@modular-magician modular-magician merged commit 40d48a0 into hashicorp:master Jan 31, 2020
danawillow pushed a commit that referenced this pull request Jan 31, 2020
#1704)

Signed-off-by: Modular Magician <magic-modules@google.com>
danawillow pushed a commit that referenced this pull request Jan 31, 2020
#1704)

Signed-off-by: Modular Magician <magic-modules@google.com>
@modular-magician modular-magician deleted the downstream-pr-49bd27fc1b4ecf2f98b97395cf3bd9e3f04b20e7 branch November 16, 2024 03:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

google_bigtable_instance force replacement of development instance_type
1 participant