KesselCheckService_CheckForUpdate
Request Body required
Section titled “Request Body required ”object
Required parameters (from an authz perspective)
- resource type and id
- permission (cannot be derived from type as types may have multiple edit permissions Ex: https://github.com/RedHatInsights/rbac-config/blob/master/configs/prod/schemas/src/notifications.ksl#L37)
- user (possibly derived from an identity token)
object
object
A reference to a Subject or, if a relation is provided, a Subject Set.
object
An optional relation which points to a set of Subjects instead of the single Subject.
e.g. “members” or “owners” of a group identified in subject.
object
object
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.