mirror of
https://github.com/opentofu/opentofu.git
synced 2025-01-15 11:13:09 -06:00
554cedab8a
A provider may not have the data to fill in required block values in all cases during the resource Read operation. This is more common in import, because there is no initial configuration or state, and it's possible some values are only provided in the configuration. The original intent of MinItems and MaxItems in the schema was to enforce configuration constraints, not to enforce what the resource could save in the state. Since the configuration is already statically validated, and the Schema is validated against the configuration in a separate step, we can drop these extra validation constraints in CoerceValue and relax it to only ensure the types conform to what is expected. |
||
|---|---|---|
| .. | ||
| coerce_value_test.go | ||
| coerce_value.go | ||
| decoder_spec_test.go | ||
| decoder_spec.go | ||
| doc.go | ||
| empty_value_test.go | ||
| empty_value.go | ||
| implied_type_test.go | ||
| implied_type.go | ||
| internal_validate_test.go | ||
| internal_validate.go | ||
| nestingmode_string.go | ||
| none_required.go | ||
| schema.go | ||
| validate_traversal_test.go | ||
| validate_traversal.go | ||