rigger should support multiple "environments"

[jchauncey]

It would be cool if rigger allowed you to "source" multiple environments and name them.

so something like the following:

rigger environment create production
rigger environment create staging

Then you could do

rigger environment set production
rigger environment set staging

This would source all the necessary environment variables in your shell so you could interact with taht environment

[sgoings]

I like this idea - kind of combines both interests of what @krancour and I were discussing on #8.

I would like to see support for multiple environments but also keep an idea of a current/active environment. Do you think that's a valid request?

Say I wanted to build two environments, provision them in parallel, and use two shells to do so... Something like this should be possible:

- shell 1
rigger environment create production
rigger environment create staging

- shell 1
rigger provision production

- shell 3
rigger provision staging

But I think I also want to be able to:

- shell 4
rigger environment create staging3
rigger provision # last created environment is considered the current environment to act on

Do you think that's too confusing or does it make sense to support both calling styles? Terraform deals with this via looking in the current directory for an environment configuration (terraform files) but you can also pass in the terraform files too...

[jchauncey]

That sounds perfect. I think we could run with this for a bit until we find
a reason to change the workflow.

[rimusz]

+1

[jchauncey]

so I was also thinking this could help manage parts of the CF templates.

rigger environment set production
rigger config set instance_type=m3.large

[sgoings]

At that point though... wouldn't you just want to drop into the file and edit it?

[jchauncey]

I think it depends on how we want to use the tool. If rigger is the thing that sits on top of installations of deis and helps you manage them. Then maybe I don't want to worry about editing a file.

Although you could do:

rigger environment set production
rigger environment edit

rigger environment edit production

These would open the appropriate CF template/Terraform script? in the users editor.