hashicorp / terraform-plugin-codegen-openapi

OpenAPI to Terraform Provider Code Generation Specification

hashicorp/terraform-plugin-codegen-openapi Issues

Migrate from mitchellh/cli to hashicorp/cli
Closed 7 months ago
Consider adding nested block support as alternative to nested attribute
Updated 7 months ago1
Consider exposing a Go module for consuming OpenAPI provider spec generation logic programmatically
Updated 7 months ago
Consider mapping JSON schema `ipv4` and `ipv6` formats to `iptypes` custom types
Updated 8 months ago
Consider mapping JSON schema `date-time` format to `timetypes.RFC3339` custom type
Updated 8 months ago
Maps that utilize `allOf` or `oneOf` result in an empty single nested attribute
Closed 8 months ago
Support for `oneOf` with discriminator
Updated 8 months ago6
[Question] Does the current codegen framework generate http calls for scaffolded resources?
Closed 8 months ago4
datasource incorrect type when name overlaps with parameters
Updated 8 months ago1
Consider permitting remote/URL references in `$ref`
Updated 9 months ago
Determine Handling for API Pagination Properties
Updated 9 months ago2
Allow configurable options for array properties with nested objects
Closed 9 months ago1
Allow definition of additional attributes in generator configuration
Updated 9 months ago3
Enhance functionality related to overriding or defining new properties for an attribute
Closed 9 months ago1
Add support for multiple input of openapi files?
Closed 9 months ago4
output does not seem to be taken into account
Closed 9 months ago2
Add homebrew installation
Updated 9 months ago2
Add support for an OCI
Updated 9 months ago1
Consider how to handle valid `allOf` constraints
Updated 9 months ago1
Ability to exclude schema attribute from resource or data source in generator config
Closed 9 months ago2
Consider how best to handle array response mapping (like data source query endpoints)
Closed 9 months ago10
Support for Any Type schema
Updated 9 months ago4
Consider adjusting collection data sources default name
Updated 9 months ago
Support `properties` with no `type` as an object
Closed 9 months ago4
Improve error messaging for property names that aren't valid Framework identifiers
Closed 9 months ago
Consider handling `string-able` multi-types
Closed 10 months ago
Add release workflows for `tfplugingen-openapi` CLI tool for tech preview
Closed 10 months ago
Normalize property names from OAS into valid Terraform attribute name
Closed 10 months ago
Consider adding config options to override schema IR descriptions
Closed a year ago1
Ensure that `description` is populated if at least one description exists between merged operations
Closed a year ago2
Enable Configuration to Consolidate Path Parameters with Existing Schema
Closed a year ago
Unconfigurable Data Source Attributes Output as Optional
Closed a year ago
Determine Computability Behavior When Required + Default
Closed a year ago
Support OAS deprecated Property as Attribute Deprecation Message
Closed a year ago
Support OAS default Property as Resource Attribute Default
Closed a year ago
Omit False Sensitive Properties from Specification
Closed a year ago
Omit Empty Description Strings in Specification
Closed a year ago
Support OAS uniqueItems property as Attribute Validator
Closed a year ago
Support OAS pattern Property as Attribute Validator
Closed a year ago
Support OAS maxItems/minItems Properties as Attribute Validators
Closed a year ago
Support OAS maximum/minimum Properties as Attribute Validators
Closed a year ago
Support OAS maxLength/minLength Properties as Attribute Validators
Closed a year ago
Support OAS enum Property as Attribute Validator
Closed a year ago
Prefer parameter description over schema description
Closed a year ago1
Better reflect computability relationship between related operations
Closed a year ago