Config Connector

MockGCP provides stub implementations of Google Cloud Platform (GCP) APIs specifically for testing Config Connector.

Key Characteristics:

• No Backend: The mocks do not launch actual resources (e.g., creating a mock VM does not launch a real VM).
• Goal: To provide consistent CRUD (Create, Read, Update, Delete) operations that are "good enough" to validate Config Connector providers.
• Implementation Pattern: Most services are implemented using standard GCP protos and grpc-gateway to enable HTTP/gRPC interoperability. This allows injecting HTTP handlers directly into serving paths without needing to listen on a real network port.

kubectl-plan is an experimental kubectl plugin designed to perform dry-runs of apply operations. It provides a human-readable format to visualize the changes that would be made to your Kubernetes resources before they are actually applied.

Note: This tool is highly experimental and under active development; it should not be considered stable for production use.

The google_compute_network_edge_security_service resource allows you to manage Google Cloud Armor network edge security services.

Warning: This resource is in beta. You must use the terraform-provider-google-beta provider to manage it.

resource "google_compute_network_edge_security_service" "default" {
  provider     = google-beta  

  name         = "my-edge-security-service"
  region       = "us-east1"
  description  = "My basic resource"
}

The google_compute_region_disk resource allows you to create and manage regional persistent disks in Google Compute Engine. Regional persistent disks provide data redundancy by replicating data across two zones within a single region, ensuring high availability. They can be used as standard HDD or SSD (pd-ssd) and can be detached from instances to preserve data.

resource "google_compute_region_disk" "example" {
  name = "my-region-disk"
  type = "pd-ssd"
  region = "us-central1"
  replica_zones = ["us-central1-a", "us-central1-f"]
}

The google_deployment_manager_deployment resource allows you to manage a collection of GCP resources that are deployed and managed together using a configuration file.

Warning: Deployment Manager and Terraform both manage GCP resource lifecycles and state. Do not attempt to manage the individual resources inside a Deployment Manager deployment using Terraform as well; this will cause ownership conflicts between the two tools. Use this resource only to manage the Deployment itself.

resource "google_deployment_manager_deployment" "deployment" {
  name = "my-deployment"

  target {
    config {
      content = file("path/to/config.yml")
    }
  }
}

The google_healthcare_hl7_v2_store resource allows you to create and manage an HL7v2 datastore within a Google Cloud Healthcare dataset. This datastore conforms to the HL7 v2 standard for healthcare information exchange.

Important Note: Changing the name property may recreate the HL7v2 store, which results in the removal of all existing data.

resource "google_healthcare_hl7_v2_store" "store" {
  name    = "example-hl7-v2-store"
  dataset = google_healthcare_dataset.dataset.id

  notification_configs {
    pubsub_topic = google_pubsub_topic.topic.id
  }

  labels = {
    label1 = "labelvalue1"
  }
}

The google_dns_record_set resource manages a set of DNS records within Google Cloud DNS.

Important Behavior:

• Authoritative: This resource is treated as an authoritative record set. Creating this resource will overwrite existing records (including default records) for the specified type in the zone.
• NS Records: The Google Cloud DNS API requires NS records to be present at all times. Terraform will not actually remove NS records during a destroy operation, although it will report that it did.

The google_compute_snapshot resource allows you to create incremental backups of Google Cloud Persistent Disks. Snapshots are more cost-effective than full images because they only store the changes made since the last snapshot. You can create snapshots even while disks are attached to running instances.

Key Features:

• Incremental Backups: Reduces storage costs and creation time.
• Encryption: Supports both Google-managed keys and customer-supplied encryption keys (CSEK).
• Custom Chains: Advanced users can use chain_name for specialized tracking (e.g., chargeback).

resource "google_compute_snapshot" "snapshot" {
  name        = "my-snapshot"
  source_disk = google_compute_disk.persistent.id
  zone        = "us-central1-a"
  labels = {
    my_label = "value"
  }
  storage_locations = ["us-central1"]
}