You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Martin Atkins a45d4467f1 stackeval: Don't fail when data resource is removed ... Due to an oversight in our handling of resource instance objects that are neither in configuration nor plan -- which is true for data resources that have since been removed from the configuration -- we were generating plan change objects that were lacking a provider configuration address, which made them syntactically invalid and thus not reloadable using the raw plan parser. This is a bit of a strange situation since we don't technically _need_ a provider configuration address for these; all we're going to do is just unceremoniously delete them from the state during apply anyway. However, we always have the provider configuration address available anyway, so adding this in here is overall simpler than changing the parser, the models it populates, and all of the downstream users of those models to treat this field as optional. This commit is more test case than it is fix, since the fix was relatively straightforward once I had a test case to reproduce the problem it's fixing.		2 years ago
..
component.go	stacks: include resources in state when calculating required providers (#34645)	2 years ago
doc.go	stackplan: Add HashiCorp copyright comments	3 years ago
from_proto.go	terraform: Plans can be "complete" and "applyable"	2 years ago
plan.go	stacks: include resources in state when calculating required providers (#34645)	2 years ago
planned_change.go	stackeval: Don't fail when data resource is removed	2 years ago
planned_change_test.go	stackplan: Include extra info in raw component instance plan	2 years ago