BuildOccurrence class

Details of a build occurrence.

Constructors

BuildOccurrence({Input<InTotoSlsaProvenanceV1>? inTotoSlsaProvenanceV1, Input<InTotoProvenance>? intotoProvenance, Input<InTotoStatement>? intotoStatement, Input<BuildProvenance>? provenance, Input<String>? provenanceBytes})

Creates a new BuildOccurrence. inTotoSlsaProvenanceV1 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. intotoProvenance Deprecated. See InTotoStatement for the replacement. In-toto Provenance representation as defined in spec. intotoStatement 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. provenance The actual provenance for the build. provenanceBytes 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.

const

BuildOccurrence.fromMap(Map<String, dynamic> map)

factory

Properties

hashCode → int

The hash code for this object.

no setter, inherited

intotoProvenance → Input<InTotoProvenance>?

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

final

inTotoSlsaProvenanceV1 → Input<InTotoSlsaProvenanceV1>?

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.

final

intotoStatement → Input<InTotoStatement>?

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.

final

provenance → Input<BuildProvenance>?

The actual provenance for the build.

final

provenanceBytes → Input<String>?

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.

final

runtimeType → Type

A representation of the runtime type of the object.

no setter, inherited

Methods

noSuchMethod(Invocation invocation) → dynamic

Invoked when a nonexistent method or property is accessed.

inherited

toMap() → Map<String, dynamic>

toString() → String

A string representation of this object.

inherited

Operators

operator ==(Object other) → bool

The equality operator.

inherited