Google Container Registry Analysis Occurrence

This page shows how to write Terraform for Container Registry Analysis Occurrence and write them securely.

google_container_analysis_occurrence (Terraform)

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.

Review your Terraform file for Google best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).


The time when the repository was created.

  • id optional computed - string
  • kind optional computed - string

The note kind which explicitly denotes which of the occurrence details are specified. This field can be used as a filter in list requests.

  • name optional computed - string

The name of the occurrence.

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.

Required. Immutable. A URI that represents the resource for which the occurrence applies. For example, for a Docker image.

The time when the repository was last updated.

  • attestation list block

    The serialized payload that is verified by one or more signatures. A base64-encoded string.

    • signatures set block

      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 for more details on this scheme. 'openpgp4fpr:74FAF3B861BDA0870C7B6DEF607E48D2A663AEEA' RFC6920 digest-named SubjectPublicKeyInfo (digest of the DER serialization): * "ni:///sha-256;cD9o9Cq6LG3jD0iKXqEi_vdjJGecm_iXkbqVoScViaU"

      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.

  • timeouts single block

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:

Frequently asked questions

What is Google Container Registry Analysis Occurrence?

Google Container Registry Analysis Occurrence is a resource for Container Registry of Google Cloud Platform. Settings can be wrote in Terraform.


Automate config file reviews on your commits

Fix issues in your infrastructure as code with auto-generated patches.