This message was deleted.

sparse-intern-71089

07/19/2023, 4:16 PM

This message was deleted.

stocky-restaurant-98004

07/19/2023, 4:18 PM

I don't know the answer for certain, but this is what I would try: https://www.pulumi.com/docs/concepts/options/ignorechanges/

little-fish-42857

07/19/2023, 4:21 PM

I'm not sure how this can apply because what im looking for is a way to define some values I send to the dynamic resource not as an input but more as a "provider config". In regular resources the provider information is supplied separately to resource params which solves this problem as the provider initialization happens at runtime and will always use the credentials from the config/env. So resource operations will always have the latest provider information...

little-fish-42857

07/19/2023, 4:26 PM

Looking for a better way to achieve this essentially -> https://github.com/pulumi/examples/blob/master/classic-azure-ts-dynamicresource/cdnCustomDomain.ts#L52-L81 but as you can see it's kind of guessing what the credentials will be and trying a bunch of stuff. May be I could use

pulumi.Config

to retrieve values in the provider itself if i can't pass them from my main program code

echoing-dinner-19531

07/19/2023, 9:45 PM

Config sadly doesn't work in dynamic providers. But even if it did the problem of refreshing short lived credentials is more wide spread than just dynamic providers, see https://github.com/pulumi/pulumi/issues/9107.

67 Views

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.