mirror of https://github.com/pulumi/pulumi.git
dcb92a284a
This change adds a flag to the `pulumi new` command, --esc-config, which redirects all standard `pulumi config` commands to use ESC rather than the typical stack config file behavior. This is just a prototype and does some magic with respect to the naming convention for environments as they relate to stacks, rather than storing some metadata on the stack itself. It also immediately performs any configuration changes via ESC, unlike the standard configuration model whereby config changes are "staged" until the next `pulumi up` and commit of the resulting stack YAML file into source control. I also had the idea to create a hierarchy of environments when this command is used: one org-wide one, then a project-wide one, and then one per stack, each with the obvious parent/child relationship. I didn't get to that just yet and it may very well be too much magic. Nevertheless, this change achieves the very basic desired result of making ESC back any and all configuration and secrets changes while using the current CLI nouns and verbs as-is. (Note: I think there's a bug with respect to secrets decryption...) |
||
|---|---|---|
| .. | ||
| asset | ||
| authhelpers | ||
| backend | ||
| cmd/pulumi | ||
| codegen | ||
| display | ||
| engine | ||
| graph | ||
| importer | ||
| operations | ||
| resource | ||
| secrets | ||
| testing/integration | ||
| util | ||
| version | ||
| workspace | ||
| README.md | ||
| go.mod | ||
| go.sum | ||
README.md
pulumi/pkg
While pulumi/sdk maintains strict backwards compatibility guarantees, code under pkg/ is handled more informally: while breaking changes are still discouraged they may happen when they make sense.