Spaces:
Running
Running
support-ticket-analyzer / backend /docs /docs-cloud-reference-api-cluster-credential-createclustercredentials.txt
Download backend/docs/docs-cloud-reference-api-cluster-credential-createclustercredentials.txt from tomeese/support-ticket-analyzer: direct link, hf CLI and curl.
- Browser
- Download file 5.55 kB
-
https://huggingface.co/spaces/tomeese/support-ticket-analyzer/resolve/main/backend/docs/docs-cloud-reference-api-cluster-credential-createclustercredentials.txt
- Command line
-
hf download hf://spaces/tomeese/support-ticket-analyzer/backend/docs/docs-cloud-reference-api-cluster-credential-createclustercredentials.txt
-
curl -L -o docs-cloud-reference-api-cluster-credential-createclustercredentials.txt https://huggingface.co/spaces/tomeese/support-ticket-analyzer/resolve/main/backend/docs/docs-cloud-reference-api-cluster-credential-createclustercredentials.txt
5.55 kB
| TITLE: Create new credentials for a database | |
| URL: | |
| ============================================================ | |
| Create new credentials for a database | |
| Create a new API key for a database. | |
| Supports read , write , read-write privileges for CORE databases. Defaults to read-write . | |
| read | |
| write | |
| read-write | |
| read-write | |
| publicOauth2 update:database | |
| A cluster ID. | |
| Create cluster credentials request | |
| A list of privileges granted to these credentials | |
| Password to be used for these credentials | |
| New cluster credentials. Note: This is the only time the password is returned. If the password is lost new credentials should be generated. | |
| ID uniquely identifying the request/response cycle. | |
| Unique identifier for this resource within Halyard Cloud | |
| A list of privileges granted to these credentials | |
| The status of a user credential | |
| Timestamp when the resource was created | |
| Password to be used for these credentials | |
| Invalid input | |
| ID uniquely identifying the request/response cycle. | |
| RFC 9457 Problem Details for HTTP APIs. | |
| Provides a standardized format for conveying error details in HTTP responses. | |
| URN-based error type identifiers following the pattern: | |
| urn:halyard:errors:{category}:{specific} | |
| Resource information (cluster, database, organization, etc.) is provided | |
| in the ProblemDetails context field, not in the URN. | |
| A short, human-readable summary of the problem type | |
| The HTTP status code | |
| A human-readable explanation specific to this occurrence | |
| A URI reference that identifies the specific occurrence | |
| object | |
| object | |
| object | |
| Context for resource-related errors (not-found, already-exists) | |
| Type of resource (e.g., cluster, database, organization) | |
| Identifier of the resource | |
| Structured context for validation errors | |
| JSON Pointer paths to missing required fields | |
| Details about invalid field values | |
| JSON Pointer path to the invalid field | |
| URN identifying the specific validation error type | |
| An optional human-readable description of the validation error | |
| Developer-friendly message explaining the error. | |
| Deprecated: Use ‘detail’ field instead. | |
| Access token is missing or invalid | |
| ID uniquely identifying the request/response cycle. | |
| RFC 9457 Problem Details for HTTP APIs. | |
| Provides a standardized format for conveying error details in HTTP responses. | |
| URN-based error type identifiers following the pattern: | |
| urn:halyard:errors:{category}:{specific} | |
| Resource information (cluster, database, organization, etc.) is provided | |
| in the ProblemDetails context field, not in the URN. | |
| A short, human-readable summary of the problem type | |
| The HTTP status code | |
| A human-readable explanation specific to this occurrence | |
| A URI reference that identifies the specific occurrence | |
| object | |
| object | |
| object | |
| Context for resource-related errors (not-found, already-exists) | |
| Type of resource (e.g., cluster, database, organization) | |
| Identifier of the resource | |
| Structured context for validation errors | |
| JSON Pointer paths to missing required fields | |
| Details about invalid field values | |
| JSON Pointer path to the invalid field | |
| URN identifying the specific validation error type | |
| An optional human-readable description of the validation error | |
| Developer-friendly message explaining the error. | |
| Deprecated: Use ‘detail’ field instead. | |
| Permission denied | |
| ID uniquely identifying the request/response cycle. | |
| RFC 9457 Problem Details for HTTP APIs. | |
| Provides a standardized format for conveying error details in HTTP responses. | |
| URN-based error type identifiers following the pattern: | |
| urn:halyard:errors:{category}:{specific} | |
| Resource information (cluster, database, organization, etc.) is provided | |
| in the ProblemDetails context field, not in the URN. | |
| A short, human-readable summary of the problem type | |
| The HTTP status code | |
| A human-readable explanation specific to this occurrence | |
| A URI reference that identifies the specific occurrence | |
| object | |
| object | |
| object | |
| Context for resource-related errors (not-found, already-exists) | |
| Type of resource (e.g., cluster, database, organization) | |
| Identifier of the resource | |
| Structured context for validation errors | |
| JSON Pointer paths to missing required fields | |
| Details about invalid field values | |
| JSON Pointer path to the invalid field | |
| URN identifying the specific validation error type | |
| An optional human-readable description of the validation error | |
| Developer-friendly message explaining the error. | |
| Deprecated: Use ‘detail’ field instead. | |
| Internal Server Error | |
| ID uniquely identifying the request/response cycle. | |
| RFC 9457 Problem Details for HTTP APIs. | |
| Provides a standardized format for conveying error details in HTTP responses. | |
| URN-based error type identifiers following the pattern: | |
| urn:halyard:errors:{category}:{specific} | |
| Resource information (cluster, database, organization, etc.) is provided | |
| in the ProblemDetails context field, not in the URN. | |
| A short, human-readable summary of the problem type | |
| The HTTP status code | |
| A human-readable explanation specific to this occurrence | |
| A URI reference that identifies the specific occurrence | |
| object | |
| object | |
| object | |
| Context for resource-related errors (not-found, already-exists) | |
| Type of resource (e.g., cluster, database, organization) | |
| Identifier of the resource | |
| Structured context for validation errors | |
| JSON Pointer paths to missing required fields | |
| Details about invalid field values | |
| JSON Pointer path to the invalid field | |
| URN identifying the specific validation error type | |
| An optional human-readable description of the validation error | |
| Developer-friendly message explaining the error. | |
| Deprecated: Use ‘detail’ field instead. |