public interface BuildOccurrenceOrBuilder extends MessageOrBuilder
Modifier and Type | Method and Description |
---|---|
BuildProvenance |
getProvenance()
Required.
|
String |
getProvenanceBytes()
Serialized JSON representation of the provenance, used in generating the
build signature in the corresponding build note.
|
ByteString |
getProvenanceBytesBytes()
Serialized JSON representation of the provenance, used in generating the
build signature in the corresponding build note.
|
BuildProvenanceOrBuilder |
getProvenanceOrBuilder()
Required.
|
boolean |
hasProvenance()
Required.
|
findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
isInitialized
boolean hasProvenance()
Required. The actual provenance for the build.
.grafeas.v1.BuildProvenance provenance = 1;
BuildProvenance getProvenance()
Required. The actual provenance for the build.
.grafeas.v1.BuildProvenance provenance = 1;
BuildProvenanceOrBuilder getProvenanceOrBuilder()
Required. The actual provenance for the build.
.grafeas.v1.BuildProvenance provenance = 1;
String getProvenanceBytes()
Serialized JSON representation of the provenance, used in generating the build signature in the corresponding build note. 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;
ByteString getProvenanceBytesBytes()
Serialized JSON representation of the provenance, used in generating the build signature in the corresponding build note. 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.