Note is the Schema for the Notes API. A Container Analysis note is a high-level piece of metadata that describes a type of analysis that can be done for a resource.
NoteSpec defines the desired state of Note
No description provided.
Note kind that represents a logical attestation "role" or "authority". For example, an organization might have one AttestationAuthority for "QA" and one for "build". This Note is intended to act strictly as a grouping mechanism for the attached Occurrences (Attestations). This grouping mechanism also provides a security boundary, since IAM ACLs gate the ability for a principle to attach an Occurrence to a given Note. It also provides a single point of lookup to find all attached Attestation Occurrences, even if they don't all live in the same project. Structure is documented below.
This submessage provides human-readable hints about the purpose of the AttestationAuthority. Because the name of a Note acts as its resource reference, it is important to disambiguate the canonical name of the Note (which might be a UUID for security purposes) from "readable" names more suitable for debug output. Note that these hints should NOT be used to look up AttestationAuthorities in security sensitive contexts, such as when looking up Attestations to verify. Structure is documented below.
Names of other notes related to this note.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
apiVersion: containeranalysis.gcp.upbound.io/v1beta1 kind: Note metadata: annotations: meta.upbound.io/example-id: containeranalysis/v1beta1/occurrence upjet.upbound.io/manual-intervention: Requires reference to KMS CryptoKey version labels: testing.upbound.io/example-name: occurrence name: occurrence spec: forProvider: attestationAuthority: - hint: - humanReadableName: Attestor Note
Discover the building blocks for your internal cloud platform.
© 2022 Upbound, Inc.
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.