You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following assumptions are made during the generation of the To<...>()/From<...>() methods based on the specified associated_external_type:
The API SDK type is a struct with fields which are named with the camel-cased attribute name (i.e., int64_attribute => Int64Attribute).
The values held within the API SDK type are pointer values of the attribute value (i.e., int64 => *int64).
Proposal
Additional flexibility could be introduced by allowing the specification of "mapping" between the Terraform Plugin Framework types and the types specified by associated_external_type. This would increase the usefulness of the generated To<...>()/From<...>() methods and accommodate cases where a direct 1-2-1 mapping between the Terraform Plugin Framework types and the API SDK types was not present.
The text was updated successfully, but these errors were encountered:
Currently, the generation of
To<...>()/From<...>()
methods (refer to Consider handling of associated_external_type for all types) uses a direct mapping from the Terraform Plugin Framework types to the API SDK types.For example, usage of
associated_external_type
in the following specification results in the generation of theTo<...>()/From<...>()
methods.The following assumptions are made during the generation of the
To<...>()/From<...>()
methods based on the specifiedassociated_external_type
:int64_attribute
=>Int64Attribute
).int64
=>*int64
).Proposal
Additional flexibility could be introduced by allowing the specification of "mapping" between the Terraform Plugin Framework types and the types specified by
associated_external_type
. This would increase the usefulness of the generatedTo<...>()/From<...>()
methods and accommodate cases where a direct 1-2-1 mapping between the Terraform Plugin Framework types and the API SDK types was not present.The text was updated successfully, but these errors were encountered: