Google Container Registry Registry

google_container_registry (Terraform)

The Registry in Container Registry can be configured in Terraform with the resource name google_container_registry. The following sections describe 5 examples of how to use the resource and its parameters.

Example Usage from GitHub

JordanP/terraform-playground

resource "google_container_registry" "default_us" {
  project = local.project_id
  location = "US"
  depends_on = [google_project_service.container_registry]
}

mattb45uk/jenkins

resource "google_container_registry" "registry" {
  project  = var.project
  location = "EU"

inokappa/oreno-gke-cluster

resource "google_container_registry" "oreno-gke" {
  project = "oreno-gke"
}

isimluk/falcon-container-terraform

resource "google_container_registry" "registry" {
  project = var.project_id
}

jhseceng/cscandemo

resource "google_container_registry" "registry" {
  project = var.project_id
}

Parameters

• bucket_self_link optional computed - string

The URI of the created resource.

• id optional computed - string
• location optional - string

The location of the registry. One of ASIA, EU, US or not specified. See the official documentation for more information on registry locations.

• project optional computed - string

The ID of the project in which the resource belongs. If it is not provided, the provider project is used.

Explanation in Terraform Registry

Ensures that the Google Cloud Storage bucket that backs Google Container Registry exists. Creating this resource will create the backing bucket if it does not exist, or do nothing if the bucket already exists. Destroying this resource does NOT destroy the backing bucket. For more information see the official documentation This resource can be used to ensure that the GCS bucket exists prior to assigning permissions. For more information see the access control page for GCR.