-
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
Allow configuring node_config of node_pools specified in container_cluster #299
Conversation
a3d48ce
to
c236728
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.
$ make testacc TEST=./google TESTARGS='-run=TestAccContainerCluster_withNodePoolNodeConfig'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./google -v -run=TestAccContainerCluster_withNodePoolNodeConfig -timeout 120m
=== RUN TestAccContainerCluster_withNodePoolNodeConfig
--- PASS: TestAccContainerCluster_withNodePoolNodeConfig (305.71s)
PASS
google/node_config.go
Outdated
@@ -103,3 +104,68 @@ var schemaNodeConfig = &schema.Schema{ | |||
}, | |||
}, | |||
} | |||
|
|||
func fillNodeConfig(v interface{}) *container.NodeConfig { |
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 you call this expandNodeConfig
to match this sort of function in other resources?
c236728
to
77265f4
Compare
544c889
to
2aaf64c
Compare
Thanks! |
<!-- This change is generated by MagicModules. --> /cc @rileykarson
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 👉 hashibot-feedback@hashicorp.com. Thanks! |
With this, node pools can be configured when defined explicitly in the
google_container_cluster
resource:Acceptance tests:
I've also changed
google_container_node_pool
to use the same node_config parsing: