famous-salesclerk-7471106/27/2022, 10:53 PM
one thing we’re noticing is when executing pulumi from CI/CD, our runners didn’t need things like:
to explicitly need the aws provider or role to assume to function — it used to fall back to the default profile in the stack and assume the default profile’s role. Now we’re seeing that the pulumi_aws methods are attempting (and failing) to run w/o assuming the default profile. is there a graceful way for us to opt into that old functionality w/o going and passing the provider explicitly in all method calls?
calls w/o a provider or parent passed into it, and it just worked
in each stack’s config….hmm
), our project relied on the default aws provider to do its thing. so, we never needed to pass any named provider, bc the default provider was in scope at some point, after going to
, this default provider basically disappeared from the execution context, even though we have all the env vars and
still in scope + unchanged