Add support for string-able multi-types, allOf overrides, and improve error messaging (#63)

* upgrade to go 1.21

* throw error when method or path not found in OAS

* add slog warning for circular references

* upgrade spec and add validate warning

* update version/validate for spec

* remove stdout as default option for output

* hook up logging plumbing

* add top level logging

* warn

* add docs for config package

* add explorer docs

* doc strings

* comment cleanup

* kubernetes testdata

* implement new error handling for properties

* fix allOf handling + add stringified multi-type

* add license header

* update schema composition logic to always error if we can't support it

* Revert "update schema composition logic to always error if we can't support it"

This reverts commit 553d4ec.

* add unit tests for allOf

* add doc strings to property error

* add docs

* add more logic for parent nodes

* added helper function for logging

Author: austinvalle

DESIGN.md

@@ -185,14 +185,15 @@ As OpenAPI is designed to describe HTTP APIs in general, it doesn't always fully
 
 ### Multi-type Support
 
-Generally, [multi-types](https://cswr.github.io/JsonSchema/spec/multiple_types/) are not supported by the generator as the Terraform Plugin Framework does not support multi-types. There is one specific scenario that is supported by the generator and that is any type that is combined with the `null` OAS type, as any Terraform data type can hold a [null](https://developer.hashicorp.com/terraform/plugin/framework/handling-data/terraform-concepts#null-values) value.
+Generally, [multi-types](https://cswr.github.io/JsonSchema/spec/multiple_types/) are not supported by the generator as the Terraform Plugin Framework does not support multi-types. There are two specific scenarios that are supported by the generator. 
+
+> **Note:** with multi-type support described below, the `description` will be populated from the root-level schema, see examples. 
 
 ### Nullable Multi-type support
-> **Note:** with nullable multi-types, the `description` will be populated from the root-level schema, as shown below. 
 
-In an OAS schema, the following keywords defining nullable multi-types are supported (nullable types will follow the same mapping rules [defined above](#oas-types-to-provider-attributes) for the type that is not the `null` type):
+If a multi-type is detected where one of the types is `null`, the other type will be used for schema mapping using the same rules [defined above](#oas-types-to-provider-attributes).
 
-#### OAS `type` keyword array
+#### Examples with `type` array
 ```json
 // Maps to StringAttribute
 {
@@ -217,7 +218,7 @@ In an OAS schema, the following keywords defining nullable multi-types are suppo
 }
 ```
 
-#### OAS `anyOf` and `oneOf` keywords
+#### Examples with `anyOf` and `oneOf`
 ```json
 // Maps to SingleNestedAttribute
 {
@@ -249,3 +250,57 @@ In an OAS schema, the following keywords defining nullable multi-types are suppo
   }
 }
 ```
+
+### String-able Multi-type support
+
+If a multi-type is detected where one of the types is a `string` and the other type is a `primitive`, then the resulting attribute will be a `StringAttribute`.
+
+Supported `primitive` types that can be represented as `string`:
+- `number`
+- `integer`
+- `boolean`
+
+
+#### Examples with `type` array, `oneOf`, and `anyOf`
+```json
+// Maps to StringAttribute
+{
+  "stringable_number_example": {
+    "description": "this is the description that's used!",
+    "type": [
+      "string",
+      "number"
+    ]
+  }
+}
+
+// Maps to StringAttribute
+{
+  "stringable_integer_example": {
+    "description": "this is the description that's used!",
+    "anyOf": [
+      {
+        "type": "integer"
+      },
+      {
+        "type": "string"
+      }
+    ]
+  }
+}
+
+// Maps to StringAttribute
+{
+  "stringable_boolean_example": {
+    "description": "this is the description that's used!",
+    "oneOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "boolean"
+      }
+    ]
+  }
+}
+```

Makefile

@@ -36,4 +36,9 @@ testdata:
 		--output ./internal/cmd/testdata/edgecase/provider_code_spec.json \
 		./internal/cmd/testdata/edgecase/openapi_spec.yml
 
+	go run ./cmd/tfplugingen-openapi generate \
+		--config ./internal/cmd/testdata/kubernetes/generator_config.yml \
+		--output ./internal/cmd/testdata/kubernetes/provider_code_spec.json \
+		./internal/cmd/testdata/kubernetes/openapi_spec.json
+
 .PHONY: lint fmt test

internal/cmd/testdata/kubernetes/generator_config.yml

@@ -0,0 +1,18 @@
+# Ref: https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs/resources/deployment_v1
+provider:
+  name: kubernetes
+
+resources:
+  deployment_v1:
+    create:
+      path: /apis/apps/v1/namespaces/{namespace}/deployments
+      method: POST
+    read:
+      path: /apis/apps/v1/namespaces/{namespace}/deployments/{name}
+      method: GET
+    update:
+      path: /apis/apps/v1/namespaces/{namespace}/deployments/{name}
+      method: PUT
+    delete:
+      path: /apis/apps/v1/namespaces/{namespace}/deployments/{name}
+      method: DELETE