-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
container: refactor node_config
node pool update
#11826
container: refactor node_config
node pool update
#11826
Conversation
5486b3d
to
8e3c116
Compare
Hello! I am a robot. Tests will require approval from a repository maintainer to run. @NickElliot, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look. You can help make sure that review is quick by doing a self-review and by running impacted tests locally. |
nodePoolInfo.project, | ||
nodePoolInfo.location, | ||
"updating GKE node pool disk_size_gb/disk_type/machine_type/storage_pools", userAgent, | ||
timeout) |
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.
A lot of opportunity to DRY up these parts with a function at some point too, but trying to keep it pretty self-contained here for now.
8e3c116
to
d467fd7
Compare
node_config
node pool updatenode_config
node pool update
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Tests analyticsTotal tests: 212 Click here to see the affected service packages
View the build log |
@NickElliot This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
@GoogleCloudPlatform/terraform-team @NickElliot This PR has been waiting for review for 1 week. Please take a look! Use the label |
@GoogleCloudPlatform/terraform-team @NickElliot This PR has been waiting for review for 2 weeks. Please take a look! Use the label |
This sets the stage for consolidating the logic for updating nodepools between the `container_cluster` and `container_node_pool` resources, by creating a new `nodePoolNodeConfigUpdate()` function. Part of hashicorp/terraform-provider-google#19225
d467fd7
to
2291e12
Compare
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.
sorry for the delays! Didn't realize the scope of this specific change in the larger issue was deceptively small and kept pushing back the review to put more time into it.
LGTM! will wait on this last build
Hah, yes, the actual change is one line plus moving a big block of code. It should set the stage for sharing the code with the default node pool update. Can check out the version before the second commit if you want to see which you prefer. |
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Tests analyticsTotal tests: 212 Click here to see the affected service packages
🟢 All tests passed! View the build log |
This resolves an issue where many subfields of `node_config` in a cluster (which affects the default node-pool "default-pool" when `remove_default_node_pool` is not set to `false`) don't support updates properly. Fixes #19225 Follow up to GoogleCloudPlatform#11826
This resolves an issue where many subfields of `node_config` in a cluster (which affects the default node-pool "default-pool" when `remove_default_node_pool` is not set to `false`) don't support updates properly. Fixes hashicorp/terraform-provider-google#19225 Followup to GoogleCloudPlatform#11826 where the code used by the regular node pool update code was broken out.
This resolves an issue where many subfields of `node_config` in a cluster (which affects the default node-pool "default-pool" when `remove_default_node_pool` is not set to `false`) don't support updates properly. Fixes hashicorp/terraform-provider-google#19225 Followup to GoogleCloudPlatform#11826 where the code used by the regular node pool update code was broken out.
This resolves an issue where many subfields of `node_config` in a cluster (which affects the default node-pool "default-pool" when `remove_default_node_pool` is not set to `false`) don't support updates properly. Fixes hashicorp/terraform-provider-google#19225 Followup to GoogleCloudPlatform#11826 where the code used by the regular node pool update code was broken out.
This resolves an issue where many subfields of `node_config` in a cluster (which affects the default node-pool "default-pool" when `remove_default_node_pool` is not set to `false`) don't support updates properly. Fixes hashicorp/terraform-provider-google#19225 Followup to GoogleCloudPlatform#11826 where the code used by the regular node pool update code was broken out.
This resolves an issue where many subfields of `node_config` in a cluster (which affects the default node-pool "default-pool" when `remove_default_node_pool` is not set to `false`) don't support updates properly. Fixes hashicorp/terraform-provider-google#19225 Followup to GoogleCloudPlatform#11826 where the code used by the regular node pool update code was broken out.
This resolves an issue where many subfields of `node_config` in a cluster (which affects the default node-pool "default-pool" when `remove_default_node_pool` is not set to `false`) don't support updates properly. Fixes hashicorp/terraform-provider-google#19225 Followup to GoogleCloudPlatform#11826 where the code used by the regular node pool update code was broken out.
This sets the stage for consolidating the logic for updating nodepools between the
container_cluster
andcontainer_node_pool
resources, by creating a newnodePoolNodeConfigUpdate()
function.Part of hashicorp/terraform-provider-google#19225
Release Note Template for Downstream PRs (will be copied)