This message was deleted.

sparse-intern-71089

12/19/2018, 10:56 AM

This message was deleted.

stocky-spoon-28903

12/19/2018, 1:46 PM

This definitely sounds like a bug to me!

stocky-spoon-28903

12/19/2018, 1:46 PM

Do you happen to have the program that you used available still?

faint-motherboard-95438

12/19/2018, 2:16 PM

@stocky-spoon-28903 well, that’s on a private repo but I can definitely make a quick and short example if needed. In fact what you need to do is only create a new

gcp.container.Cluster

then try a

pulumi destroy

or even just commenting out the

Cluster

definition and run a

pulumi up

again.

stocky-spoon-28903

12/19/2018, 2:18 PM

Ok I’ll open an issue for this later this morning - the behaviour is not expected. Last question: what version of the provider, language package and CLI are you using?

faint-motherboard-95438

12/19/2018, 2:22 PM

Copy code

"@pulumi/gcp": "^0.16.0",
"@pulumi/kubernetes": "^0.18.0",
"@pulumi/pulumi": "^0.16.8"

Copy code

$ pulumi version
v0.16.8

stocky-spoon-28903

12/19/2018, 2:24 PM

Thanks.

stocky-spoon-28903

12/19/2018, 2:25 PM

FWIW I’m working on an update to the GCP provider this morning, so I’ll add more regression tests around this too

faint-motherboard-95438

12/19/2018, 2:27 PM

OK great, thanks ! Let me know if you need more information or if I can help to test anything

Open in Slack

Previous Next

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.