Recently, HashiCorp has published terraform-plugin-framework-nettypes, which contains an iptypes package with IPv4Address and IPv6Addresscustom string types, which provide validation and semantic equality handling (for IPv6) that are often required for IP address strings. The Provider code specification already supports custom types.
Proposal
Proposal
For any string types that define a format of ipv4, add the iptypes.IPv4AddressType type and iptypes.IPv4Address value to the custom type in the outputted provider code spec.
For any string types that define a format of ipv6, add the iptypes.IPv6AddressType type and iptypes.IPv6Address value to the custom type in the outputted provider code spec.
Use Cases or Problem Statement
JSON schema (the backbone of all the request/response body schemas in OpenAPI 3.0/3.1) supports designating a
type: string
as an IPv4 or IPv6 address string via theformat
field: https://json-schema.org/understanding-json-schema/reference/string#ip-addresses.Recently, HashiCorp has published terraform-plugin-framework-nettypes, which contains an
iptypes
package withIPv4Address
andIPv6Address
custom string types, which provide validation and semantic equality handling (for IPv6) that are often required for IP address strings. The Provider code specification already supports custom types.Proposal
Proposal
format
ofipv4
, add theiptypes.IPv4AddressType
type andiptypes.IPv4Address
value to the custom type in the outputted provider code spec.Schema
IR Attribute
format
ofipv6
, add theiptypes.IPv6AddressType
type andiptypes.IPv6Address
value to the custom type in the outputted provider code spec.Schema
IR Attribute
Additional Information
No response
Code of Conduct