Update dependencies

humanitec · Jul 1, 2024 · 331eca8 · 331eca8
1 parent 2ddffdf
commit 331eca8
Show file tree

Hide file tree

Showing 205 changed files with 505 additions and 219 deletions.
diff --git a/docs/openapi.json b/docs/openapi.json
@@ -2,7 +2,7 @@
   "openapi": "3.0.0",
   "info": {
     "title": "Humanitec API",
-    "version": "0.26.6",
+    "version": "0.26.10",
     "description": "# Introduction\nThe *Humanitec API* allows you to automate and integrate Humanitec into your developer and operational workflows.\nThe API is a REST based API. It is based around a set of concepts:\n\n* Core\n* External Resources\n* Sets and Deltas\n\n## Authentication\n\nAlmost all requests made to the Humanitec API require Authentication. See our [Developer Docs on API Authentication](https://developer.humanitec.com/platform-orchestrator/reference/api-references/#authentication) for instructions.\n\n## Content Types\nAll of the Humanitec API unless explicitly only accepts content types of `application/json` and will always return valid `application/json` or an empty response.\n\n## Response Codes\n### Success\nAny response code in the `2xx` range should be regarded as success.\n\n| **Code** | **Meaning** |\n| --- | --- |\n| `200` | Success |\n| `201` | Success (In future, `201` will be replaced by `200`) |\n| `204` | Success, but no content in response |\n\n_Note: We plan to simplify the interface by replacing 201 with 200 status codes._\n\n### Failure\nAny response code in the `4xx` should be regarded as an error which can be rectified by the client. `5xx` error codes indicate errors that cannot be corrected by the client.\n\n| **Code** | **Meaning** |\n| --- | --- |\n| `400` | General error. (Body will contain details) |\n| `401` | Attempt to access protected resource without `Authorization` Header. |\n| `403` | The `Bearer` or `JWT` does not grant access to the requested resource. |\n| `404` | Resource not found. |\n| `405` | Method not allowed |\n| `409` | Conflict. Usually indicated a resource with that ID already exists. |\n| `422` | Unprocessable Entity. The body was not valid JSON, was empty or contained an object different from what was expected. |\n| `429` | Too many requests - request rate limit has been reached. |\n| `500` | Internal Error. If it occurs repeatedly, contact support. |\n",
     "contact": {
       "name": "API Support",
@@ -6880,11 +6880,11 @@
             "description": "The account was successfully deleted.\n\n"
           },
           "400": {
-            "description": "One or more request parameters is missing or invalid.\n\n",
+            "description": "The Resource Account cannot be deleted as at least one non-deleted Resource Definition or one Active Resource still referencing it.\nIn the error the coordinates of the referencing resources are provided.\n",
             "content": {
               "application/json": {
                 "schema": {
-                  "$ref": "#/components/schemas/HumanitecErrorResponse"
+                  "$ref": "#/components/schemas/ConflictingResourcesErrorResponse"
                 }
               }
             }
@@ -7423,7 +7423,7 @@
           }
         ],
         "requestBody": {
-          "description": "The Resource Definition record details.\n\nThe PATCH operation would change the value of the property if it is included in the request payload JSON, and not `null`. Missing and `null` properties are ignored.\n\nFor the map properties, such as PatchResourceDefinitionRequest.DriverInputs, the merge operation is applied.\n\nMerge rules are as follows:\n\n- If a map property has a value, it is replaced (or added).\n\n- If a map property is set to `null`, it is removed.\n\n- If a map property is not included (missing in JSON), it remains unchanged.\n\nIf driver_type changes and an Active Resource which uses this Resource Definition exists, the resource provisioned with the previous used driver_type will be deleted.",
+          "description": "The Resource Definition record details.\n\nThe PATCH operation would change the value of the property if it is included in the request payload JSON, and not `null`. Missing and `null` properties are ignored.\n\nFor the map properties, such as PatchResourceDefinitionRequest.DriverInputs, the merge operation is applied.\n\nMerge rules are as follows:\n\n- If a map property has a value, it is replaced (or added).\n\n- If a map property is set to `null`, it is removed.\n\n- If a map property is not included (missing in JSON), it remains unchanged.",
           "required": true,
           "content": {
             "application/json": {
@@ -16908,6 +16908,59 @@
         ],
         "type": "object"
       },
+      "ConflictingResourcesErrorResponse": {
+        "description": "Represents a standard Humanitec Error with additional details which describe why an action on a specific resource cannot be performed due to some other entities linked to it.\n",
+        "properties": {
+          "details": {
+            "$ref": "#/components/schemas/ConflictingResourcesErrorResponseDetails"
+          },
+          "error": {
+            "type": "string"
+          },
+          "message": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "error",
+          "message",
+          "details"
+        ],
+        "type": "object"
+      },
+      "ConflictingResourcesErrorResponseDetails": {
+        "description": "Object composed by the list of resources which prevent the deletion of the specified entity. The resources are indexed by their kind.",
+        "type": "object",
+        "properties": {
+          "referencing_resources": {
+            "$ref": "#/components/schemas/ConflictingResourcesErrorResponseDetailsResources"
+          }
+        },
+        "required": [
+          "referencing_resources"
+        ],
+        "additionalProperties": false
+      },
+      "ConflictingResourcesErrorResponseDetailsResources": {
+        "type": "object",
+        "properties": {
+          "resource_definitions": {
+            "description": "List of non-deleted Resource Definitions referencing the specified Resource Account.",
+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/ResourceDefinitionResponse"
+            }
+          },
+          "active_resources": {
+            "description": "List of Active Resources referencing the specified Resource Account.",
+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/ActiveResourceResponse"
+            }
+          }
+        },
+        "additionalProperties": false
+      },
       "ManifestResponse": {
         "description": "Manifest represents a complete or a partial Kubernetes manifest, and a location for its injection.",
         "properties": {
@@ -17129,7 +17182,6 @@
         "description": "PatchResourceDefinitionRequest describes a ResourceDefinition change request.",
         "example": {
           "driver_account": "gcp-dev-cloudsql",
-          "driver_type": "humanitec/terraform",
           "driver_inputs": {
             "secret_refs": {
               "dbcredentials": {
@@ -17165,10 +17217,6 @@
             "$ref": "#/components/schemas/ValuesSecretsRefsRequest",
             "description": "(Optional) Additional input data to be passed to the driver."
           },
-          "driver_type": {
-            "description": "(Optional) The driver to be used to create the resource.",
-            "type": "string"
-          },
           "name": {
             "description": "(Optional) Resource display name",
             "nullable": true,
@@ -17243,7 +17291,7 @@
             "type": "string"
           },
           "is_used": {
-            "description": "Indicates if this account is being used (referenced) by any resource definition.",
+            "description": "Indicates if this account is being used (referenced) by any resource definition or active resource.",
             "type": "boolean"
           },
           "name": {
@@ -19909,6 +19957,7 @@
         "ResourceDefinition",
         "ResourceDefinitionVersion",
         "ResourceProvision",
+        "AccountType",
         "ResourceAccount",
         "ResourceType",
         "ResourceClass"
@@ -19996,7 +20045,7 @@
     },
     {
       "name": "AccountType",
-      "x-displayName": "Account Types",
+      "x-displayName": "Resource Account Types",
       "description": "Resource Account Types define cloud providers or protocols to which a resource account can belong.\n<SchemaDefinition schemaRef=\"#/components/schemas/AccountTypeRequest\" />\n"
     },
     {

diff --git a/src/generated/.openapi-generator/FILES b/src/generated/.openapi-generator/FILES
@@ -29,6 +29,9 @@ models/Batch.ts
 models/BatchItem.ts
 models/ClusterSecretRequest.ts
 models/ClusterSecretResponse.ts
+models/ConflictingResourcesErrorResponse.ts
+models/ConflictingResourcesErrorResponseDetails.ts
+models/ConflictingResourcesErrorResponseDetailsResources.ts
 models/ContainerArtefactVersion.ts
 models/ControllerResponse.ts
 models/CreateArtefactVersion.ts

diff --git a/src/generated/apis/PublicApi.ts b/src/generated/apis/PublicApi.ts
@@ -4,7 +4,7 @@
  * Humanitec API
  * # Introduction The *Humanitec API* allows you to automate and integrate Humanitec into your developer and operational workflows. The API is a REST based API. It is based around a set of concepts:  * Core * External Resources * Sets and Deltas  ## Authentication  Almost all requests made to the Humanitec API require Authentication. See our [Developer Docs on API Authentication](https://developer.humanitec.com/platform-orchestrator/reference/api-references/#authentication) for instructions.  ## Content Types All of the Humanitec API unless explicitly only accepts content types of `application/json` and will always return valid `application/json` or an empty response.  ## Response Codes ### Success Any response code in the `2xx` range should be regarded as success.  | **Code** | **Meaning** | | --- | --- | | `200` | Success | | `201` | Success (In future, `201` will be replaced by `200`) | | `204` | Success, but no content in response |  _Note: We plan to simplify the interface by replacing 201 with 200 status codes._  ### Failure Any response code in the `4xx` should be regarded as an error which can be rectified by the client. `5xx` error codes indicate errors that cannot be corrected by the client.  | **Code** | **Meaning** | | --- | --- | | `400` | General error. (Body will contain details) | | `401` | Attempt to access protected resource without `Authorization` Header. | | `403` | The `Bearer` or `JWT` does not grant access to the requested resource. | | `404` | Resource not found. | | `405` | Method not allowed | | `409` | Conflict. Usually indicated a resource with that ID already exists. | | `422` | Unprocessable Entity. The body was not valid JSON, was empty or contained an object different from what was expected. | | `429` | Too many requests - request rate limit has been reached. | | `500` | Internal Error. If it occurs repeatedly, contact support. | 
  *
- * The version of the OpenAPI document: 0.26.6
+ * The version of the OpenAPI document: 0.26.10
  * Contact: [email protected]
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -28,6 +28,7 @@ import type {
   AutomationRuleRequest,
   AutomationRuleResponse,
   Batch,
+  ConflictingResourcesErrorResponse,
   CreateArtefactVersion,
   CreateDriverRequestRequest,
   CreateResourceAccountRequestRequest,
@@ -154,6 +155,8 @@ import {
     AutomationRuleResponseToJSON,
     BatchFromJSON,
     BatchToJSON,
+    ConflictingResourcesErrorResponseFromJSON,
+    ConflictingResourcesErrorResponseToJSON,
     CreateArtefactVersionFromJSON,
     CreateArtefactVersionToJSON,
     CreateDriverRequestRequestFromJSON,

diff --git a/src/generated/models/AWSAuthRequest.ts b/src/generated/models/AWSAuthRequest.ts
@@ -4,7 +4,7 @@
  * Humanitec API
  * # Introduction The *Humanitec API* allows you to automate and integrate Humanitec into your developer and operational workflows. The API is a REST based API. It is based around a set of concepts:  * Core * External Resources * Sets and Deltas  ## Authentication  Almost all requests made to the Humanitec API require Authentication. See our [Developer Docs on API Authentication](https://developer.humanitec.com/platform-orchestrator/reference/api-references/#authentication) for instructions.  ## Content Types All of the Humanitec API unless explicitly only accepts content types of `application/json` and will always return valid `application/json` or an empty response.  ## Response Codes ### Success Any response code in the `2xx` range should be regarded as success.  | **Code** | **Meaning** | | --- | --- | | `200` | Success | | `201` | Success (In future, `201` will be replaced by `200`) | | `204` | Success, but no content in response |  _Note: We plan to simplify the interface by replacing 201 with 200 status codes._  ### Failure Any response code in the `4xx` should be regarded as an error which can be rectified by the client. `5xx` error codes indicate errors that cannot be corrected by the client.  | **Code** | **Meaning** | | --- | --- | | `400` | General error. (Body will contain details) | | `401` | Attempt to access protected resource without `Authorization` Header. | | `403` | The `Bearer` or `JWT` does not grant access to the requested resource. | | `404` | Resource not found. | | `405` | Method not allowed | | `409` | Conflict. Usually indicated a resource with that ID already exists. | | `422` | Unprocessable Entity. The body was not valid JSON, was empty or contained an object different from what was expected. | | `429` | Too many requests - request rate limit has been reached. | | `500` | Internal Error. If it occurs repeatedly, contact support. | 
  *
- * The version of the OpenAPI document: 0.26.6
+ * The version of the OpenAPI document: 0.26.10
  * Contact: [email protected]
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

diff --git a/src/generated/models/AWSSMRequest.ts b/src/generated/models/AWSSMRequest.ts
@@ -4,7 +4,7 @@
  * Humanitec API
  * # Introduction The *Humanitec API* allows you to automate and integrate Humanitec into your developer and operational workflows. The API is a REST based API. It is based around a set of concepts:  * Core * External Resources * Sets and Deltas  ## Authentication  Almost all requests made to the Humanitec API require Authentication. See our [Developer Docs on API Authentication](https://developer.humanitec.com/platform-orchestrator/reference/api-references/#authentication) for instructions.  ## Content Types All of the Humanitec API unless explicitly only accepts content types of `application/json` and will always return valid `application/json` or an empty response.  ## Response Codes ### Success Any response code in the `2xx` range should be regarded as success.  | **Code** | **Meaning** | | --- | --- | | `200` | Success | | `201` | Success (In future, `201` will be replaced by `200`) | | `204` | Success, but no content in response |  _Note: We plan to simplify the interface by replacing 201 with 200 status codes._  ### Failure Any response code in the `4xx` should be regarded as an error which can be rectified by the client. `5xx` error codes indicate errors that cannot be corrected by the client.  | **Code** | **Meaning** | | --- | --- | | `400` | General error. (Body will contain details) | | `401` | Attempt to access protected resource without `Authorization` Header. | | `403` | The `Bearer` or `JWT` does not grant access to the requested resource. | | `404` | Resource not found. | | `405` | Method not allowed | | `409` | Conflict. Usually indicated a resource with that ID already exists. | | `422` | Unprocessable Entity. The body was not valid JSON, was empty or contained an object different from what was expected. | | `429` | Too many requests - request rate limit has been reached. | | `500` | Internal Error. If it occurs repeatedly, contact support. | 
  *
- * The version of the OpenAPI document: 0.26.6
+ * The version of the OpenAPI document: 0.26.10
  * Contact: [email protected]
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

diff --git a/src/generated/models/AWSSMResponse.ts b/src/generated/models/AWSSMResponse.ts
@@ -4,7 +4,7 @@
  * Humanitec API
  * # Introduction The *Humanitec API* allows you to automate and integrate Humanitec into your developer and operational workflows. The API is a REST based API. It is based around a set of concepts:  * Core * External Resources * Sets and Deltas  ## Authentication  Almost all requests made to the Humanitec API require Authentication. See our [Developer Docs on API Authentication](https://developer.humanitec.com/platform-orchestrator/reference/api-references/#authentication) for instructions.  ## Content Types All of the Humanitec API unless explicitly only accepts content types of `application/json` and will always return valid `application/json` or an empty response.  ## Response Codes ### Success Any response code in the `2xx` range should be regarded as success.  | **Code** | **Meaning** | | --- | --- | | `200` | Success | | `201` | Success (In future, `201` will be replaced by `200`) | | `204` | Success, but no content in response |  _Note: We plan to simplify the interface by replacing 201 with 200 status codes._  ### Failure Any response code in the `4xx` should be regarded as an error which can be rectified by the client. `5xx` error codes indicate errors that cannot be corrected by the client.  | **Code** | **Meaning** | | --- | --- | | `400` | General error. (Body will contain details) | | `401` | Attempt to access protected resource without `Authorization` Header. | | `403` | The `Bearer` or `JWT` does not grant access to the requested resource. | | `404` | Resource not found. | | `405` | Method not allowed | | `409` | Conflict. Usually indicated a resource with that ID already exists. | | `422` | Unprocessable Entity. The body was not valid JSON, was empty or contained an object different from what was expected. | | `429` | Too many requests - request rate limit has been reached. | | `500` | Internal Error. If it occurs repeatedly, contact support. | 
  *
- * The version of the OpenAPI document: 0.26.6
+ * The version of the OpenAPI document: 0.26.10
  * Contact: [email protected]
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

diff --git a/src/generated/models/AccountCredsRequest.ts b/src/generated/models/AccountCredsRequest.ts
@@ -4,7 +4,7 @@
  * Humanitec API
  * # Introduction The *Humanitec API* allows you to automate and integrate Humanitec into your developer and operational workflows. The API is a REST based API. It is based around a set of concepts:  * Core * External Resources * Sets and Deltas  ## Authentication  Almost all requests made to the Humanitec API require Authentication. See our [Developer Docs on API Authentication](https://developer.humanitec.com/platform-orchestrator/reference/api-references/#authentication) for instructions.  ## Content Types All of the Humanitec API unless explicitly only accepts content types of `application/json` and will always return valid `application/json` or an empty response.  ## Response Codes ### Success Any response code in the `2xx` range should be regarded as success.  | **Code** | **Meaning** | | --- | --- | | `200` | Success | | `201` | Success (In future, `201` will be replaced by `200`) | | `204` | Success, but no content in response |  _Note: We plan to simplify the interface by replacing 201 with 200 status codes._  ### Failure Any response code in the `4xx` should be regarded as an error which can be rectified by the client. `5xx` error codes indicate errors that cannot be corrected by the client.  | **Code** | **Meaning** | | --- | --- | | `400` | General error. (Body will contain details) | | `401` | Attempt to access protected resource without `Authorization` Header. | | `403` | The `Bearer` or `JWT` does not grant access to the requested resource. | | `404` | Resource not found. | | `405` | Method not allowed | | `409` | Conflict. Usually indicated a resource with that ID already exists. | | `422` | Unprocessable Entity. The body was not valid JSON, was empty or contained an object different from what was expected. | | `429` | Too many requests - request rate limit has been reached. | | `500` | Internal Error. If it occurs repeatedly, contact support. | 
  *
- * The version of the OpenAPI document: 0.26.6
+ * The version of the OpenAPI document: 0.26.10
  * Contact: [email protected]
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).