Google Cloud CLI Without gpgcheck=0

gcloud, gsutil and bq on EL 10 from the versioned tarball, checked against a SHA-256 pinned beside the version: Google's yum key has a SHA-1 self-signature that rpm on EL 10 refuses, so the repository only installs with the GPG check off. Usage reporting and update nagging off installation-wide, read back through gcloud config get. Original role, live-tested on Rocky Linux 10.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

ansibleGoogle CloudCI/CD & Automationv1.0.0live-tested

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

A Dataflow Job on Private Workers that Drains on Destroy A Delivery Pipeline whose Production Target Waits for a Person Builds that Run as a Named Account, Privately, with Approval to Deploy Cloud Composer 2 (managed Airflow)Cloud Workflows (least-privilege identity)Dataproc Single-Node Cluster

The same job on other clouds

This module has no cross-cloud peer set in the catalogue, so there is no portability comparison to draw.

Installing it

module "ansible_google_cloud_cli" {
  source  = "www.iac-bazaar.com/iac-bazaar/ansible-google-cloud-cli/gcp"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.