This message was deleted.
# generals
sparse-intern-71089
07/19/2023, 4:16 PMThis message was deleted.
s
stocky-restaurant-98004
07/19/2023, 4:18 PMI don't know the answer for certain, but this is what I would try: https://www.pulumi.com/docs/concepts/options/ignorechanges/
l
little-fish-42857
07/19/2023, 4:21 PMI'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 PMLooking 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.Confige
echoing-dinner-19531
07/19/2023, 9:45 PMConfig 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.
68 Views