This message was deleted.

If you're prepared to rework all your code, you could pass a

provider

opt into all your resources.

I have Components and I'm passing the provider with the assumeRole to my components. I ended up going with awsudo to assume the role before executing pulumi and that works how I'd expect. It's unfortunate to have to do that though since normally Pulumi helps with eliminating bash scripts.

That's unfortunate. I have adopted the policy of passing a

provider

to every resource constructor or get function, and I choose the provider based on the stack. It's working great for me. (Once I find the time to adopt automation-api, I can probably simplify the solution somewhat.)