https://pulumi.com
Join Slack
This message was deleted.
# kubernetes
s
This message was deleted.
a
Pulumi should use the same provider during a delete as it did during a create. You don’t need to tell it to. If its using the default provider to delete a resource created with a explicit provider, thats a bug. Would you be willing to file an issue at https://github.com/pulumi/pulumi/issues/new/choose?
c
I'll write a simplified version of my code to reproduce it first. If I am able to reproduce it I'll open an issue. Thanks Ian!
🙏 1
Update: When inspecting my state, I realized that my K8S resources where not using my dynamically provisioned provider, but the default provider. At first, I did not understand why but at some point, I replaces 
ResourceOptions(provider=x)
with 
ResourceOptions(providers=[x])
and it fixed my issue as all the component resources are now created using the proper provider. Is that an known issue?
a
It sounds like the behavior you are describing is correct. Confusion between 
provider
and 
providers
is a known issue. 
provider/providers
is an API that is incredibly easy to confuse. I thought we had a warning for that in the Python SDK. Since it doesn’t sound like you saw any such warning, an issue describing your experience would be appreciated. We’re in an unfortunate place with backwards compatibility on the underlying API, but it is something we plan to address for Pulumi 4.0. Your feedback is appreciated.
c
I've seen no such warning. What's the difference between provider and providers?
a
provider
tells Pulumi what provider to use with the resource. For a GKE cluster, the only valid 
provider
would be Provider for google. 
providers
tells Pulumi what providers to use for child resources, and is intended to be passed to component resources.
c
Oh, that explains my issue, thanks! 🙂
I did my best to express my frustrations, attempts, and ideas: https://github.com/pulumi/pulumi/issues/11732 But I'm not sure it's very actionable yet.
5 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