-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add support for instance_type to google_bigtable_instance. #313
Changes from all commits
645853f
e59f51d
5a2daad
b9bf516
ff069d7
31354dd
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the number of nodes is
ForceNew
, we don't want to force our users to delete and recreate their production database.I would rather have our users specify num_nodes = 1 for DEVELOPMENT.
If you don't send num_nodes to the server, does it set 1 for dev and 3 for production by default? If so, we could use
Computed = True
for num_nodes.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we send a non-zero value to the server for
num_nodes
for aDEVELOPMENT
instance, the request fails. There's no server default when you don't send anum_nodes
for a production one; the request fails.Users won't actually need to recreate their instances; the
num_nodes
of 3 is preserved in state, and they will just need to update their config when it diffs.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we leave the
num_nodes
default to 3 and just don't send the property when creating aDEVELOPMENT
instance? This way, we don't create churn for our users...There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doing things like that breaks the 1:1 mapping from config -> the API, and imo isn't worth it if we ever need to correct later. For example, if we were to gain the ability to read
num_nodes
, we would either need to conditionally read it or would see diffs in the future.I think it's worth a breaking change here because the number of users is small (and I expect the # of users that relied on the implicit default is smaller), the change is easy to make, and it means we'll be tracking the API as accurately as we can until the next client update.