diff --git a/client/client.gen.go b/client/client.gen.go index 68f2fcb..a71d5dd 100644 --- a/client/client.gen.go +++ b/client/client.gen.go @@ -1490,7 +1490,7 @@ type OrganizationResponse struct { Name string `json:"name"` // ScaffoldingUrl URL of the scaffolding service. - ScaffoldingUrl *string `json:"scaffolding_url,omitempty"` + ScaffoldingUrl *string `json:"scaffolding_url"` // TrialExpiresAt Timestamp the trial expires at. TrialExpiresAt *time.Time `json:"trial_expires_at"` diff --git a/docs/openapi.json b/docs/openapi.json index 0a3b197..992f4a7 100644 --- a/docs/openapi.json +++ b/docs/openapi.json @@ -3,10 +3,10 @@ "info": { "title": "Humanitec API", "version": "0.26.11", - "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", + "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\nThe Humanitec API, unless explicitly specified, 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, a new resource was created |\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` 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.\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", - "email": "apiteam@humanitec.com" + "name": "Humanitec Support", + "email": "support@humanitec.com" }, "x-logo": { "url": "humanitec-logo.png", @@ -15310,6 +15310,7 @@ }, "scaffolding_url": { "description": "URL of the scaffolding service.", + "nullable": true, "type": "string" } }, @@ -17789,7 +17790,7 @@ "type": "object" } }, - "type": "postgres", + "type": "my-org/postgres", "use": "direct" }, "properties": { @@ -17812,8 +17813,9 @@ "type": "object" }, "type": { - "description": "Unique resource type identifier (system-wide, across all organizations).", - "type": "string" + "description": "Unique resource type identifier (system-wide, across all organizations). It should start with the Humanitec Organization ID followed by \"/\".", + "type": "string", + "example": "my-org/my-private-type" }, "use": { "description": "Kind of dependency between resource of this type and a workload. It should be one of: `direct`, `indirect`, `implicit`.", @@ -20017,7 +20019,7 @@ ], "externalDocs": { "description": "Find out more about how to use Humanitec in your every-day development work.", - "url": "https://docs.humanitec.com" + "url": "https://developer.humanitec.com/" }, "x-tagGroups": [ {