v0.14.0

Features

• Resolve Naming Conflicts for Custom Resources: The fromCRD function now supports a new namePrefix argument. This allows users to resolve potential naming conflicts that arise when multiple Custom Resource Definitions (CRDs) define resources with the same kind (e.g., Database). By specifying a namePrefix, generated attribute names can be made unique (e.g., resources.postgresDatabases and resources.mysqlDatabases).
  • For more details, refer to the updated section in the User Guide for Typed Resources.

Bug Fixes

• Optional Protocol for Service Ports: Fixed an issue where the protocol field was implicitly required for ServicePort definitions when using an attribute set for ports. The protocol field is now correctly treated as optional, aligning with Kubernetes API behavior. This allows defining ports like ports = { http = { containerPort = 80; }; } without explicitly specifying a protocol. @aserowy #35

Improvements

• CRD Generator Enhancements: The fromCRD generator has improved handling for OpenAPI schema constructs, such as anyOf and x-kubernetes-int-or-string. @schradert #37

New Contributors

• @aserowy made their first contribution in #35
• @schradert made their first contribution in #37