Grafeas v1 API - Class BuildOccurrence (3.7.0)

public sealed class BuildOccurrence : IMessage<BuildOccurrence>, IEquatable<BuildOccurrence>, IDeepCloneable<BuildOccurrence>, IBufferMessage, IMessage

Reference documentation and code samples for the Grafeas v1 API class BuildOccurrence.

Details of a build occurrence.

Inheritance

object > BuildOccurrence

Implements

IMessage BuildOccurrence, IEquatable BuildOccurrence, IDeepCloneable BuildOccurrence, IBufferMessage, IMessage

Inherited Members

object.GetHashCode()

object.GetType()

object.ToString()

Namespace

Grafeas.V1

Assembly

Grafeas.V1.dll

Constructors

BuildOccurrence()

public BuildOccurrence()

BuildOccurrence(BuildOccurrence)

public BuildOccurrence(BuildOccurrence other)

Parameter
Name	Description
`other`	`BuildOccurrence`

Properties

InTotoSlsaProvenanceV1

public InTotoSlsaProvenanceV1 InTotoSlsaProvenanceV1 { get; set; }

In-Toto Slsa Provenance V1 represents a slsa provenance meeting the slsa spec, wrapped in an in-toto statement. This allows for direct jsonification of a to-spec in-toto slsa statement with a to-spec slsa provenance.

Property Value
Type	Description
`InTotoSlsaProvenanceV1`

IntotoProvenance

public InTotoProvenance IntotoProvenance { get; set; }

Deprecated. See InTotoStatement for the replacement. In-toto Provenance representation as defined in spec.

Property Value
Type	Description
`InTotoProvenance`

IntotoStatement

public InTotoStatement IntotoStatement { get; set; }

In-toto Statement representation as defined in spec. The intoto_statement can contain any type of provenance. The serialized payload of the statement can be stored and signed in the Occurrence's envelope.

Property Value
Type	Description
`InTotoStatement`

Provenance

public BuildProvenance Provenance { get; set; }

The actual provenance for the build.

Property Value
Type	Description
`BuildProvenance`

ProvenanceBytes

public string ProvenanceBytes { get; set; }

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.

Property Value
Type	Description
`string`