IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Update allocator logging settings
editUpdate allocator logging settings
editAll changes in the specified object are applied to the logging settings for this allocator instance according to the JSON Merge Patch processing rules. Omitting existing fields causes the same values to be reapplied. Specifying a null value reverts the field to the default value, or removes the field when no default value exists.
Request
editPATCH /api/v1/platform/infrastructure/allocators/{allocator_id}/logging_settings
Path parameters
edit| Name | Type | Required | Description |
|---|---|---|---|
|
|
Y |
The allocator identifier. |
Request body
edit(string) (required) The logging settings to update
Responses
edit-
200 -
The updated logging settings for the allocator instance
Headers
-
x-cloud-resource-created(string) - The date-time when the resource was created (ISO format relative to UTC)
-
x-cloud-resource-last-modified(string) - The date-time when the resource was last modified (ISO format relative to UTC)
-
x-cloud-resource-version(string) - The resource version, which is used to avoid update conflicts with concurrent operations
-
-
400 -
The update request is invalid. (code:
patch.request_malformed)Headers
-
x-cloud-error-codes(string; allowed values: [patch.request_malformed]) - The error codes associated with the response
-
-
404 -
The logging settings for this allocator were not found. (code:
allocators.logging_settings.not_found)Headers
-
x-cloud-error-codes(string; allowed values: [allocators.logging_settings.not_found]) - The error codes associated with the response
-
Request example
editcurl -XPATCH https://{{hostname}}/api/v1/platform/infrastructure/allocators/{allocator_id}/logging_settings \
-H "Authorization: ApiKey $ECE_API_KEY" \
-H 'Content-Type: application/json'