Google Container Registry Analysis Occurrence
This page shows how to write Terraform for Container Registry Analysis Occurrence and write them securely.
The Analysis Occurrence in Container Registry can be configured in Terraform with the resource name
google_container_analysis_occurrence. The following sections describe how to use the resource and its parameters.
Example Usage from GitHub
An example could not be found in GitHub.
create_timeoptional computed - string
The time when the repository was created.
The note kind which explicitly denotes which of the occurrence details are specified. This field can be used as a filter in list requests.
nameoptional computed - string
The name of the occurrence.
note_namerequired - string
The analysis note associated with this occurrence, in the form of projects/[PROJECT]/notes/[NOTE_ID]. This field can be used as a filter in list requests.
A description of actions that can be taken to remedy the note.
resource_urirequired - string
Required. Immutable. A URI that represents the resource for which the occurrence applies. For example, https://gcr.io/project/image@sha256:123abc for a Docker image.
update_timeoptional computed - string
The time when the repository was last updated.
serialized_payloadrequired - string
The serialized payload that is verified by one or more signatures. A base64-encoded string.
public_key_idrequired - string
The identifier for the public key that verifies this signature. MUST be an RFC3986 conformant URI. When possible, the key id should be an immutable reference, such as a cryptographic digest. Examples of valid values: OpenPGP V4 public key fingerprint. See https://www.iana.org/assignments/uri-schemes/prov/openpgp4fpr for more details on this scheme. 'openpgp4fpr:74FAF3B861BDA0870C7B6DEF607E48D2A663AEEA' RFC6920 digest-named SubjectPublicKeyInfo (digest of the DER serialization): * "ni:///sha-256;cD9o9Cq6LG3jD0iKXqEi_vdjJGecm_iXkbqVoScViaU"
signatureoptional - string
The content of the signature, an opaque bytestring. The payload that this signature verifies MUST be unambiguously provided with the Signature during verification. A wrapper message might provide the payload explicitly. Alternatively, a message might have a canonical serialization that can always be unambiguously computed to derive the payload.
Explanation in Terraform Registry
An occurrence is an instance of a Note, or type of analysis that can be done for a resource. To get more information about Occurrence, see: