Ability to modify environment variables for the exec subcommand

[psibi]

I recently had this usecase where I wanted to store multiple similar keys but for test and staging environment:

amber encrypt GH_TOKEN_DEV redacted
amber encrypt GH_TOKEN_STAGING redacted

My usecase is that I want to execute this via amber exec. But at runtime, I want to change the environment variable appropriately before executing. In the above case, I want to change the environment variable to GH_TOKEN on the appropriate environment before executing.

I was thinking something like this:

amber exec --rename-env GH_TOKEN_DEV=GH_TOKEN -- gh release download

Any objections to have this feature ? I can volunteer to implement the same if there are no objections.

[snoyberg]

That looks totally reasonable, sounds great. Only other thought: should we introduce some method to have different potential values for each environment variable? The only term I can think of is introducing environments, which is a confusing term. But what I mean is having something like:

GH_TOKEN_DEV:
    dev: DEADBEEF1
    staging: DEADBEEF2

And then:

amber exec --environment dev -- gh release download

I'd want to use a different term than environment if we can think of one. I'm not sure if I like this more or less than your proposal TBH, just brainstorming.

[psibi]

Interesting idea and I think it's nice. I have to think about this a bit more to see how it fits with the other workflow, let me get back to you on this.

I'd want to use a different term than environment if we can think of one.

Probably PROFILE ?

[snoyberg]

Probably PROFILE ?

Perfect!