pulumi-google-native-kotlin/com.pulumi.googlenative.containeranalysis.v1alpha1.kotlin.outputs/BuildDetailsResponse

BuildDetailsResponse

data class BuildDetailsResponse(val intotoProvenance: InTotoProvenanceResponse, val intotoStatement: InTotoStatementResponse, val provenance: BuildProvenanceResponse, val provenanceBytes: String)

Message encapsulating build provenance details.

Constructors

fun BuildDetailsResponse(intotoProvenance: InTotoProvenanceResponse, intotoStatement: InTotoStatementResponse, provenance: BuildProvenanceResponse, provenanceBytes: String)

Types

Companion

object Companion

Properties

intotoProvenance

val ~~intotoProvenance~~: InTotoProvenanceResponse

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

intotoStatement

val intotoStatement: InTotoStatementResponse

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

val provenance: BuildProvenanceResponse

The actual provenance

provenanceBytes

val provenanceBytes: String

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.