KesselNotificationsIntegrationService_DeleteNotificationsIntegration
Request Body required
Section titled “Request Body required ”object
The resource to be deleted will be defined by “<reporter_data.reporter_type>:<reporter_instaance_id>:<reporter_data.local_resource_id>” from the request body.
object
The ID of the instance of the reporter. This is derived from the authentication mechanism, i.e. authentication token.
The URL for this resource in the reporter’s management UI console. For example this would be the cluster URL in the HCC Console for an OCM reported cluster.
Reporter specific API link to the resource.
The ID assigned to this resource by the reporter, for example OCM cluster ID, HBI’s host id, or ACM managed cluster name etc.
Version of the reporter
Responses
Section titled “ Responses ”OK
object
default
Section titled “default ”Default error response
The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.
object
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
A list of messages that carry the error details. There is a common set of message types for APIs to use.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.
object
The type of the serialized message.