pulumi/pkg/compiler/errors
Matt Ellis 22c9e0471c Use Stack over Environment to describe a deployment target
Previously we used the word "Environment" as the term for a deployment
target, but since then we've started to use the term Stack. Adopt this
across the CLI.

From a user's point of view, there are a few changes:

1. The `env` verb has been renamed to `stack`
2. The `-e` and `--env` options to commands which operate on an
environment now take `-s` or `--stack` instead.
3. Becase of (2), the commands that used `-s` to display a summary now
only support passing the full option name (`--summary`).

On the local file system, we still store checkpoint data in the `env`
sub-folder under `.pulumi` (so we can reuse existing checkpoint files
that were written to the old folder)
2017-10-16 13:04:20 -07:00
..
binder.go Clarify aspects of using the DCO 2017-06-26 14:46:34 -07:00
compiler.go Clarify aspects of using the DCO 2017-06-26 14:46:34 -07:00
eval.go Clarify aspects of using the DCO 2017-06-26 14:46:34 -07:00
new.go Rename pulumi-fabric to pulumi 2017-09-21 19:18:21 -07:00
planapply.go Use Stack over Environment to describe a deployment target 2017-10-16 13:04:20 -07:00