mirror of https://github.com/pulumi/pulumi.git
b3a596a464
This adds back the behavior where `pulumi destroy` will add back an `encryptedkey` to the `Pulumi.<stack>.yaml` file. NodeJS Automation API can use the `stackSettings` field to rewrite the `Pulumi.<stack>.yaml` file directly and strip the `encryptedkey` field from it leading to downstream errors. On previous versions of Pulumi, `pulumi destroy` would add this field back to the `Pulumi.<stack>.yaml` file and errors would not occur. |
||
---|---|---|
.. | ||
authhelpers | ||
backend | ||
cmd/pulumi | ||
codegen | ||
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.