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 and use case
Currently the generator config allows overriding of attributes, but limits its functionality to modifying the description property:
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 several properties that are missing in the resulting provider code specification generated from the API spec, which is reasonable as the API spec lacks terraform-specific information.
Enhancement request
Here is a list of use cases I found would be useful for defining within the generator config:
RequiresReplace
andUseStateForUnkown
.ConflictsWith
which cannot be represented easily in an OpenAPI Spec.computed_optional_required
property for an attribute. While the tool has a certain logic to define this value for attributes, it would be helpful to give flexibility to the user to cover specific edge cases.