This message was deleted.

sparse-intern-71089

12/22/2020, 10:10 AM

This message was deleted.

bland-lamp-16797

12/22/2020, 11:00 AM

I think you'll just need two+ files,

Pulumi.<stack>.yaml

like this...

shy-toddler-33930

12/22/2020, 11:38 AM

Thanks I have edited my question so it is a clearer but what I am after is storing state in one account that can be used across other accounts. I don't think that will work with this setup?

gentle-diamond-70147

12/22/2020, 4:43 PM

I believe the only way to configure the S3 backend is with environment variables. So there's only one set of credentials available to pulumi to access the backend when invoking

pulumi

gentle-diamond-70147

12/22/2020, 4:44 PM

If you could add more details about your use case and how you would like for it to work to https://github.com/pulumi/pulumi/issues/4665, that would be helpful.

billowy-army-68599

12/22/2020, 6:36 PM

@shy-toddler-33930 you can sort of do this by using the AWS environment variables for accessing your state store, then setting your provider configuration inside the stack. So for examples

Copy code

export AWS_PROFILE=shared_account
pulumi config set aws:profile=target_account

💯 1

billowy-army-68599

12/22/2020, 6:37 PM

You can also set an explicit provider on resources, which is something terraform/terragrunt can't do

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.