9 Commits (fed6538dece2b0306d52f6c12facb5c4e5485725)

Author	SHA1	Message	Date
hashicorp-copywrite[bot]	325d18262e	[COMPLIANCE] Add Copyright and License Headers	3 years ago
James Bardin	ea193d5ce6	don't panic with a null list block value in config ... Using ignore_changes with a list block, where the provider returned an invalid null value for that block, can result in a panic when validating the plan. Future releases may prevent providers from storing a null block in state, however we can avoid the panic for now. Only the NestingList case needs to be handled, because legacy providers only have list and set blocks, and the set case does not use the config value.	3 years ago
James Bardin	a6a08fe84a	AssertPlanValid for computed with config value ... Return early from AssertPlanValid for any attribute which is only computed. We currently fail if there's a config value, but that could only happen because of core, not because of the provider.	4 years ago
James Bardin	782132da33	remove incorrect computed check ... The config is already validated, and does not need to be checked in AssertPlanValid. Add some more coverage for plan validation.	5 years ago
James Bardin	ea68d79ea2	nested object values can be computed ... While blocks were not allowed to be computed by the provider, nested objects can be. Remove the errors regarding blocks and verify unknown values are valid.	5 years ago
James Bardin	903797084a	objects vs maps in nested object types ... When using NestedMap objects, unify the codepath for both maps and objects as they may be interchangeable.	5 years ago
James Bardin	7ca6be8285	correctly verify planned nested object values ... The validation for nested object types with computed attributes was using the incorrect function call.	5 years ago
James Bardin	b7f8ef4dc6	handle unexpected changes to unknown block ... An unknown block represents a dynamic configuration block with an unknown for_each value. We were not catching the case where a provider modified this value unexpectedly, which would crash with block of type NestingList blocks where the config value has no length for comparison.	5 years ago
Martin Atkins	034e944070	Move plans/ to internal/plans/ ... This is part of a general effort to move all of Terraform's non-library package surface under internal in order to reinforce that these are for internal use within Terraform only. If you were previously importing packages under this prefix into an external codebase, you could pin to an earlier release tag as an interim solution until you've make a plan to achieve the same functionality some other way.	5 years ago