public interface ResultOrBuilder
extends com.google.protobuf.MessageOrBuilder
Modifier and Type | Method and Description |
---|---|
com.google.protobuf.Struct |
getData()
Audit-worthy details from the operation result.
|
com.google.protobuf.StructOrBuilder |
getDataOrBuilder()
Audit-worthy details from the operation result.
|
String |
getSchema()
Reference to a JSON-Schema definition describing the structure and
validation constraints of the semi-structured (google.protobuf.Struct)
field.
|
com.google.protobuf.ByteString |
getSchemaBytes()
Reference to a JSON-Schema definition describing the structure and
validation constraints of the semi-structured (google.protobuf.Struct)
field.
|
Result.Status |
getStatus()
Must be set to a non-default value.
|
int |
getStatusValue()
Must be set to a non-default value.
|
boolean |
hasData()
Audit-worthy details from the operation result.
|
findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
int getStatusValue()
Must be set to a non-default value.
.auditlog.v2.Result.Status status = 1;
Result.Status getStatus()
Must be set to a non-default value.
.auditlog.v2.Result.Status status = 1;
String getSchema()
Reference to a JSON-Schema definition describing the structure and validation constraints of the semi-structured (google.protobuf.Struct) field. This is a JSON Pointer, relative to the compound JSON schema we bundle and make available. See: https://json-schema.org/understanding-json-schema/structuring.html#bundling So for example, if the compound JSON schema has a base URI of "http://example.com/schemas", then "general/HttpRequest" would resolve to "http://example.com/schemas#/$defs/general/HttpRequest". Examples: "general/HttpRequest" "kafka/IncrementalAlterConfigsRequest" "api/cmk.v2.Cluster" Schema definition authors should ensure that only backwards-compatible changes are made to their definitions. Rather than introduce backwards- incompatible changes, they should start a new schema definition with a different id. Note, this field is OPTIONAL. But, if it is present, the reference MUST be resolvable, and the `data` MUST satisfy the corresponding validation constraints.
string schema = 2 [(.confluent.protobuf.field_meta) = { ... }
com.google.protobuf.ByteString getSchemaBytes()
Reference to a JSON-Schema definition describing the structure and validation constraints of the semi-structured (google.protobuf.Struct) field. This is a JSON Pointer, relative to the compound JSON schema we bundle and make available. See: https://json-schema.org/understanding-json-schema/structuring.html#bundling So for example, if the compound JSON schema has a base URI of "http://example.com/schemas", then "general/HttpRequest" would resolve to "http://example.com/schemas#/$defs/general/HttpRequest". Examples: "general/HttpRequest" "kafka/IncrementalAlterConfigsRequest" "api/cmk.v2.Cluster" Schema definition authors should ensure that only backwards-compatible changes are made to their definitions. Rather than introduce backwards- incompatible changes, they should start a new schema definition with a different id. Note, this field is OPTIONAL. But, if it is present, the reference MUST be resolvable, and the `data` MUST satisfy the corresponding validation constraints.
string schema = 2 [(.confluent.protobuf.field_meta) = { ... }
boolean hasData()
Audit-worthy details from the operation result. MUST not include credential secrets, and SHOULD NOT include large or redundant information. For many types of requests, the "success" or "failure" status is all that's audit-worthy, and the `data` field can be omitted. Requests that create, modify, or match resource IDs that were not explicitly specified in the request payload SHOULD include relevant resource IDs in the `cloud_resources` or `platform_resources` fields, and MAY also include them in the result data if necessary to provide more context. If the `schema` field is present, the `data` MUST satisfy any validation constraints of the referenced schema.
.google.protobuf.Struct data = 3;
com.google.protobuf.Struct getData()
Audit-worthy details from the operation result. MUST not include credential secrets, and SHOULD NOT include large or redundant information. For many types of requests, the "success" or "failure" status is all that's audit-worthy, and the `data` field can be omitted. Requests that create, modify, or match resource IDs that were not explicitly specified in the request payload SHOULD include relevant resource IDs in the `cloud_resources` or `platform_resources` fields, and MAY also include them in the result data if necessary to provide more context. If the `schema` field is present, the `data` MUST satisfy any validation constraints of the referenced schema.
.google.protobuf.Struct data = 3;
com.google.protobuf.StructOrBuilder getDataOrBuilder()
Audit-worthy details from the operation result. MUST not include credential secrets, and SHOULD NOT include large or redundant information. For many types of requests, the "success" or "failure" status is all that's audit-worthy, and the `data` field can be omitted. Requests that create, modify, or match resource IDs that were not explicitly specified in the request payload SHOULD include relevant resource IDs in the `cloud_resources` or `platform_resources` fields, and MAY also include them in the result data if necessary to provide more context. If the `schema` field is present, the `data` MUST satisfy any validation constraints of the referenced schema.
.google.protobuf.Struct data = 3;