pulumi/tests/integration
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
..
config_upgrade Upgrade configuration files on first run 2018-02-28 17:37:18 -08:00
diff Rename pulumi package to @pulumi/pulumi (#917) 2018-02-12 13:13:13 -08:00
empty Get the empty Python program working 2018-02-23 19:33:02 -08:00
project_main Run yarn upgrade and commit all resulting lockfiles 2018-01-30 14:46:44 -08:00
project_main_abs Fix pending delete replacement failure (#658) 2017-12-07 09:44:38 -08:00
project_main_parent Fix pending delete replacement failure (#658) 2017-12-07 09:44:38 -08:00
protect_resources Rename pulumi package to @pulumi/pulumi (#917) 2018-02-12 13:13:13 -08:00
stack_dependencies Code review feedback: 2018-02-22 13:33:50 -08:00
stack_outputs Run yarn upgrade and commit all resulting lockfiles 2018-01-30 14:46:44 -08:00
stack_parenting Rename pulumi package to @pulumi/pulumi (#917) 2018-02-12 13:13:13 -08:00
stack_project_name Rename pulumi package to @pulumi/pulumi (#917) 2018-02-12 13:13:13 -08:00
steps Eliminate type redundancy 2018-02-28 12:44:55 -08:00
integration_test.go Upgrade configuration files on first run 2018-02-28 17:37:18 -08:00