Closed AgustinBettati closed 8 months ago
Combining this request with #86 as they are closely related 👍🏻
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Context I have been trying this tool with the intention of replacing existing manual schema and type definitions with autogenerated ones using an existing API spec. In order to reach this parity there are differences in how array types are being generated in the provider spec code compared to my actual terraform schemas.
Enhancement request Currently schemas of
"type" : "array"
with nested objects are being defined as attribute lists. While this is correct, terraform has a broader set of possibilities:list_nested
orset_nested
.attribute
or as ablock
.Providing this terraform specific information in the generator config, potentially in
attributes
property, would give users more flexibility in the generated provider code spec.