Skip to content

Commit

Permalink
Update dependencies
Browse files Browse the repository at this point in the history
  • Loading branch information
@johanneswuerbach @github-actions
johanneswuerbach authored and github-actions[bot] committed Jul 29, 2024
1 parent be9ea13 commit 155b68f
Show file tree
Hide file tree
Showing 208 changed files with 1,366 additions and 824 deletions.
192 changes: 172 additions & 20 deletions docs/openapi.json
View file

Large diffs are not rendered by default.

8 changes: 6 additions & 2 deletions src/generated/.openapi-generator/FILES
View file
Original file line number Diff line number Diff line change
Expand Up @@ -29,8 +29,12 @@ 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/ConvertScoreToSetBody.ts
models/CreateArtefactVersion.ts
models/CreateArtefactVersionBase.ts
models/CreateContainerArtefactVersion.ts
Expand All @@ -39,8 +43,6 @@ models/CreateResourceAccountRequestRequest.ts
models/CreateResourceDefinitionRequestRequest.ts
models/CreateSecretStorePayloadRequest.ts
models/CreateWorkloadArtefactVersion.ts
models/CreateWorkloadArtefactVersionExtensions.ts
models/CreateWorkloadArtefactVersionExtensionsDeploy.ts
models/DeltaMetadataRequest.ts
models/DeltaMetadataResponse.ts
models/DeltaRequest.ts
Expand Down Expand Up @@ -143,6 +145,8 @@ models/RuntimeInfoResponseV1.ts
models/RuntimeInfoResponseV2.ts
models/RuntimeInfoStatus.ts
models/RuntimeInfoStatusClass.ts
models/ScoreHumanitecExtensions.ts
models/ScoreHumanitecExtensionsDeploy.ts
models/SecretReference.ts
models/SecretStoreRequest.ts
models/SecretStoreResponse.ts
Expand Down
60 changes: 57 additions & 3 deletions src/generated/apis/PublicApi.ts
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,10 @@
/* eslint-disable */
/**
* 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. |
* # 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 The Humanitec API, unless explicitly specified, 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, a new resource was created | | `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` range should be regarded as an error that 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
* Contact: apiteam@humanitec.com
* The version of the OpenAPI document: 0.26.11
* Contact: support@humanitec.com
*
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
* https://openapi-generator.tech
Expand All @@ -28,6 +28,8 @@ import type {
AutomationRuleRequest,
AutomationRuleResponse,
Batch,
ConflictingResourcesErrorResponse,
ConvertScoreToSetBody,
CreateArtefactVersion,
CreateDriverRequestRequest,
CreateResourceAccountRequestRequest,
Expand Down Expand Up @@ -154,6 +156,10 @@ import {
AutomationRuleResponseToJSON,
BatchFromJSON,
BatchToJSON,
ConflictingResourcesErrorResponseFromJSON,
ConflictingResourcesErrorResponseToJSON,
ConvertScoreToSetBodyFromJSON,
ConvertScoreToSetBodyToJSON,
CreateArtefactVersionFromJSON,
CreateArtefactVersionToJSON,
CreateDriverRequestRequestFromJSON,
Expand Down Expand Up @@ -369,6 +375,11 @@ export interface CancelPipelineRunRequest {
If_Match?: string;
}

export interface ConvertScoreToSetRequest {
orgId: string;
ConvertScoreToSetBody: ConvertScoreToSetBody;
}

export interface CreateAgentRequest {
orgId: string;
AgentCreateBody: AgentCreateBody;
Expand Down Expand Up @@ -1756,6 +1767,49 @@ export class PublicApi extends runtime.BaseAPI {
await this.cancelPipelineRunRaw(requestParameters, initOverrides);
}

/**
* Convert a Score specification, optional overrides, and extensions into the contents for a deployment set.
*/
async convertScoreToSetRaw(requestParameters: ConvertScoreToSetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<WorkloadArtefactVersionDeploymentSet>> {
if (requestParameters['orgId'] == null) {
throw new runtime.RequiredError(
'orgId',
'Required parameter "orgId" was null or undefined when calling convertScoreToSet().'
);
}

if (requestParameters['ConvertScoreToSetBody'] == null) {
throw new runtime.RequiredError(
'ConvertScoreToSetBody',
'Required parameter "ConvertScoreToSetBody" was null or undefined when calling convertScoreToSet().'
);
}

const queryParameters: any = {};

const headerParameters: runtime.HTTPHeaders = {};

headerParameters['Content-Type'] = 'application/json';

const response = await this.request({
path: `/orgs/{orgId}/artefact-versions/convert-score`.replace(`{${"orgId"}}`, encodeURIComponent(String(requestParameters['orgId']))),
method: 'POST',
headers: headerParameters,
query: queryParameters,
body: ConvertScoreToSetBodyToJSON(requestParameters['ConvertScoreToSetBody']),
}, initOverrides);

return new runtime.JSONApiResponse(response, (jsonValue) => WorkloadArtefactVersionDeploymentSetFromJSON(jsonValue));
}

/**
* Convert a Score specification, optional overrides, and extensions into the contents for a deployment set.
*/
async convertScoreToSet(requestParameters: ConvertScoreToSetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<WorkloadArtefactVersionDeploymentSet> {
const response = await this.convertScoreToSetRaw(requestParameters, initOverrides);
return await response.value();
}

/**
* Register a new Agent under an Organization.
*/
Expand Down
6 changes: 3 additions & 3 deletions src/generated/models/AWSAuthRequest.ts
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,10 @@
/* eslint-disable */
/**
* 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. |
* # 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 The Humanitec API, unless explicitly specified, 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, a new resource was created | | `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` range should be regarded as an error that 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
* Contact: apiteam@humanitec.com
* The version of the OpenAPI document: 0.26.11
* Contact: support@humanitec.com
*
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
* https://openapi-generator.tech
Expand Down
6 changes: 3 additions & 3 deletions src/generated/models/AWSSMRequest.ts
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,10 @@
/* eslint-disable */
/**
* 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. |
* # 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 The Humanitec API, unless explicitly specified, 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, a new resource was created | | `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` range should be regarded as an error that 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
* Contact: apiteam@humanitec.com
* The version of the OpenAPI document: 0.26.11
* Contact: support@humanitec.com
*
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
* https://openapi-generator.tech
Expand Down
Loading

0 comments on commit 155b68f

Please sign in to comment.