031b561ef0
When testing destroy, the test harness calls Refresh followed by Plan, with the expectation that the resulting diff will be empty. Data resources challenge this expectation, because they will always be instantiated during refresh if their configuration isn't computed, and so the subsequent diff will want to destroy what was instantiated. To work around this, we make an exception that data resource destroy diffs may appear in the plan but nothing else. This fixes #6713. |
||
|---|---|---|
| .. | ||
| error.go | ||
| id.go | ||
| id_test.go | ||
| map.go | ||
| map_test.go | ||
| resource.go | ||
| state.go | ||
| state_test.go | ||
| testing.go | ||
| testing_config.go | ||
| testing_import_state.go | ||
| testing_import_state_test.go | ||
| testing_test.go | ||
| wait.go | ||
| wait_test.go | ||