types: Introduce ListValueFrom, MapValueFrom, ObjectValueFrom, and SetValueFrom functions #522
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #520
These will enable provider developers to use the framework type system's built-in conversion rules to create collection types, rather than using more generic
tfsdk.ValueFrom()
or other methodologies.In this example, a map using standard Go types is used to create a
types.Map
framework type with known values:There may be additional use cases or needs that get teased out with this introduction, such as the ability to create a
types.Object
from amap[string]any
, however those can be handled in potential future feature requests.