pulumi/tests/integration/config_upgrade
Matt Ellis e2ce16b057 Upgrade configuration files on first run
Migrate configuration from the old model to the new model. The
strategy here is that when we first run `pulumi` we enumerate all of
the stacks from all of the backends we know about and for each stack
get the configuration values from the project and workspace and
promote them into the new file. As we do this, we remove stack
specific config from the workspace and Pulumi.yaml file.

If we are able to upgrade all the stacks we know about, we delete all
global configuration data in the workspace and in Pulumi.yaml as well.

We have a test that ensures upgrades continue to work.
2018-02-28 17:37:18 -08:00
..
.pulumi Upgrade configuration files on first run 2018-02-28 17:37:18 -08:00
.gitignore Upgrade configuration files on first run 2018-02-28 17:37:18 -08:00
Pulumi.yaml Upgrade configuration files on first run 2018-02-28 17:37:18 -08:00