fac6944781
Fixes #2633. Currently when a user runs `refresh` and a resource is in a state of error, the `refresh` will fail and the resource state will not be persisted. This can make it vastly harder to incrementally fix infrastructure. The issue mentioned above explains more of the historical context, as well as some specific failure modes. This commit resolves this issue by causing refresh to *not* report an error in this case, and instead to simply log a warning that the `refresh` has recognized that the resource is in an unhealthy state during state sync. |
||
|---|---|---|
| .. | ||
| deploytest | ||
| providers | ||
| builtins.go | ||
| plan.go | ||
| plan_executor.go | ||
| plan_test.go | ||
| snapshot.go | ||
| source.go | ||
| source_error.go | ||
| source_eval.go | ||
| source_eval_test.go | ||
| source_fixed.go | ||
| source_null.go | ||
| step.go | ||
| step_executor.go | ||
| step_generator.go | ||
| target.go | ||