mirror of https://github.com/pulumi/pulumi.git
bf47e9571f
Before this change PropertiesPath.Delete would "delete" locations from an array by just writing null to them but not changing the size of the array. This could result in a deployment that looked like it should have been a same ending up as an update. For example given a resource `X` with a property `foo` set to `[1]` if you changed the program to set `foo` to `[1, 2]` and set `ignoreChanges` to `foo[1]` the deployment would do an update with `foo` set to `[1, 0]`. This now errors that the path is invalid, this is similar to how we error on invalid paths if intermediate objects are missing. |
||
---|---|---|
.. | ||
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.