pulumi/pkg/resource
Will Jones 62293f05f7
Improve snapshot integrity panics depending on operation (#17144)
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.


![image](https://github.com/user-attachments/assets/6d91b5ea-95f5-470b-992f-1abfa116c838)

---------

Co-authored-by: Justin Van Patten <jvp@justinvp.com>
Co-authored-by: Eric Rudder <ericrudder@users.noreply.github.com>
2024-09-04 21:22:18 +00:00
..
analyzer Clean up uses of .Error() (#14965) 2023-12-20 15:54:06 +00:00
deploy Improve snapshot integrity panics depending on operation (#17144) 2024-09-04 21:22:18 +00:00
edit Rewrite `DeletedWith` properties when renaming stacks (#16216) 2024-05-16 15:09:32 +00:00
graph state_move: add --include-parents flag (#16628) 2024-07-11 12:59:20 +00:00
provider turn on the golangci-lint exhaustive linter (#15028) 2024-01-17 16:50:41 +00:00
stack state_move: include stack name in the passhprase prompt (#16861) 2024-08-02 10:59:12 +00:00
testdata ci: radical idea - what if slow tests & no stdout makes GH consider runner dead? 2022-03-06 14:52:13 -08:00