What's the recommended way of handling different p...
# general
s
What's the recommended way of handling different profiles for a DIY backend? I am using R2 and got it working via the AWS CLI but unlike sst, which automatically sources my
.env
file and uses my CF API token in there (without the need of the AWS CLI), I have to export
AWS_PROFILE
for each invocation of pulumi which is a bit inconvenient and before I go ahead and use a custom script in
package.json
that runs
dotenv
I thought it'd be best to ask what you recommend.
c
You pretty much always need some kind of task / command runner that controls your environment to run pulumi or whatever. make, task, your CI agent may have local modes..
We bake our own pulumi docker images that have sensible default env vars for AWS_PROFILE, all the pulumi vars etc.