public interface DetailsOrBuilder
extends com.google.protobuf.MessageOrBuilder
| Modifier and Type | Method and Description |
|---|---|
BuildProvenance |
getProvenance()
The actual provenance for the build.
|
String |
getProvenanceBytes()
Serialized JSON representation of the provenance, used in generating the
`BuildSignature` in the corresponding Result.
|
com.google.protobuf.ByteString |
getProvenanceBytesBytes()
Serialized JSON representation of the provenance, used in generating the
`BuildSignature` in the corresponding Result.
|
BuildProvenanceOrBuilder |
getProvenanceOrBuilder()
The actual provenance for the build.
|
boolean |
hasProvenance()
The actual provenance for the build.
|
findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneofboolean hasProvenance()
The actual provenance for the build.
.grafeas.v1beta1.provenance.BuildProvenance provenance = 1;BuildProvenance getProvenance()
The actual provenance for the build.
.grafeas.v1beta1.provenance.BuildProvenance provenance = 1;BuildProvenanceOrBuilder getProvenanceOrBuilder()
The actual provenance for the build.
.grafeas.v1beta1.provenance.BuildProvenance provenance = 1;String getProvenanceBytes()
Serialized JSON representation of the provenance, used in generating the `BuildSignature` in the corresponding Result. After verifying the signature, `provenance_bytes` can be unmarshalled and compared to the provenance to confirm that it is unchanged. A base64-encoded string representation of the provenance bytes is used for the signature in order to interoperate with openssl which expects this format for signature verification. The serialized form is captured both to avoid ambiguity in how the provenance is marshalled to json as well to prevent incompatibilities with future changes.
string provenance_bytes = 2;com.google.protobuf.ByteString getProvenanceBytesBytes()
Serialized JSON representation of the provenance, used in generating the `BuildSignature` in the corresponding Result. After verifying the signature, `provenance_bytes` can be unmarshalled and compared to the provenance to confirm that it is unchanged. A base64-encoded string representation of the provenance bytes is used for the signature in order to interoperate with openssl which expects this format for signature verification. The serialized form is captured both to avoid ambiguity in how the provenance is marshalled to json as well to prevent incompatibilities with future changes.
string provenance_bytes = 2;Copyright © 2019 Google LLC. All rights reserved.