Matt Ellis 9cf9428638 Save config information in Pulumi.yaml ... Instead of having information stored in the checkpoint file, save it in the Pulumi.yaml file. We introduce a new section `stacks` which holds information specific to a stack. Next, we'll support adding configuration information that applies to *all* stacks for a Program and allow the stack specific config to overwrite or augment it.		2017-10-20 13:30:07 -07:00
..
lumidl	Rename pulumi-fabric to pulumi	2017-09-21 19:18:21 -07:00
api.go	Add login and logout commands. (#437)	2017-10-19 15:22:07 -07:00
config.go	Save config information in Pulumi.yaml	2017-10-20 13:30:07 -07:00
config_test.go	Save config information in Pulumi.yaml	2017-10-20 13:30:07 -07:00
creds.go	Add login and logout commands. (#437)	2017-10-19 15:22:07 -07:00
destroy.go	Use Stack over Environment to describe a deployment target	2017-10-16 13:04:20 -07:00
login.go	Add login and logout commands. (#437)	2017-10-19 15:22:07 -07:00
preview.go	Use Stack over Environment to describe a deployment target	2017-10-16 13:04:20 -07:00
provider_local.go	Save config information in Pulumi.yaml	2017-10-20 13:30:07 -07:00
pulumi.go	Add login and logout commands. (#437)	2017-10-19 15:22:07 -07:00
stack.go	Use Stack over Environment to describe a deployment target	2017-10-16 13:04:20 -07:00
stack_init.go	Use Stack over Environment to describe a deployment target	2017-10-16 13:04:20 -07:00
stack_ls.go	Use Stack over Environment to describe a deployment target	2017-10-16 13:04:20 -07:00
stack_rm.go	Use Stack over Environment to describe a deployment target	2017-10-16 13:04:20 -07:00
stack_select.go	Use Stack over Environment to describe a deployment target	2017-10-16 13:04:20 -07:00
update.go	Use Stack over Environment to describe a deployment target	2017-10-16 13:04:20 -07:00
util.go	Save config information in Pulumi.yaml	2017-10-20 13:30:07 -07:00
version.go	Construct version based on git information	2017-10-16 18:35:41 -07:00