https://pulumi.com
Join Slack
This message was deleted.
# google-cloud
s
This message was deleted.
b
yes, you can use 
pulumi import
or the 
import
resource provider
if you update the nodepool, then do 
pulumi refresh
(if you've already written pulumi code) pulumi will tell you what has changed
a
Ok great I'll try that. Thank you.
It seems like when I try to refresh the stack it keeps the cluster's old config and setting the value to the actual config makes it think that there is a change that needs to be applied when in reality there shouldn't be.
n
Been there, done that.. so..
Copy code
pulumi.IgnoreChanges(
			[]string{
				`metadata.annotations["<http://deployment.kubernetes.io/revision|deployment.kubernetes.io/revision>"]`,
				`metadata.selfLink`,
				`nodeConfig`,
				`nodePools`,
			},
		),
☝️ This is basically the only way I found to stop 
pulumi
from replacing my cluster on each update
And it works great 😛
a
Thank you I'll put this in.
✅ 1
n
My pleasure ^^
2 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by