a1a713cf28
There are a few different reasons why a resource instance tracked in the prior state might be considered an "orphan", but previously we reported them all identically in the planned changes. In order to help users understand the reason for a surprising planned delete, we'll now try to specify an additional reason for the planned deletion, covering all of the main reasons why that could happen. This commit only introduces the new detail to the plans.Changes result, though it also incidentally exposes it as part of the JSON plan result in order to keep that working without returning errors in these new cases. We'll expose this information in the human-oriented UI output in a subsequent commit. |
||
|---|---|---|
| .. | ||
| archiving.html.md | ||
| credentials-helpers.html.md | ||
| debugging.html.md | ||
| graph.html.md | ||
| index.html.md | ||
| json-format.html.md | ||
| lifecycle.html.md | ||
| login-protocol.html.markdown | ||
| machine-readable-ui.html.md | ||
| module-registry-protocol.html.md | ||
| provider-meta.html.md | ||
| provider-network-mirror-protocol.html.md | ||
| provider-registry-protocol.html.md | ||
| remote-service-discovery.html.md | ||