mirror of https://github.com/pulumi/pulumi.git
62293f05f7
Snapshot integrity errors generally happen for one of two reasons: * We just *wrote* a snapshot with an issue. * We just attempted to *read* a snapshot with an issue. As much as possible, we want to capture errors and issues at the point of *writing* the snapshot, since that will generally be where the bug that caused the integrity issue lies. This commit updates snapshot integrity errors to carry awareness of whether they happened during a read or write, and modifies the panic message to nudge users to hunt down the failing write operation if the panic they are seeing relates to a read.  --------- Co-authored-by: Justin Van Patten <jvp@justinvp.com> Co-authored-by: Eric Rudder <ericrudder@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| 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.