AnsibleByExample

google.cloud 1.14.0 - Whats New and How to Test

Beginner
2024-01-012By Luca Berton

Lesson 1 of 25 in AWS Automation

AWS with Ansible — full curriculum
  1. 1. AWS Basics for Ansible
  2. 2. Installing the amazon.aws Collection and boto3
  3. 3. AWS Credentials and Profiles: Safe Configuration
  4. 4. Your First AWS Playbook: Regions, Tags and Idempotency
  5. 5. AWS Dynamic Inventory with the aws_ec2 Plugin
  6. 6. Grouping and Filtering Hosts with keyed_groups and Filters
  7. 7. Provisioning EC2 Instances
  8. 8. AMIs and Launch Templates
  9. 9. Building VPC Networks with Ansible
  10. 10. Security Groups and Network Access Control
  11. 11. Elastic IPs and Load Balancers
  12. 12. S3 Buckets and Object Management
  13. 13. IAM Users, Roles and Policies
  14. 14. RDS Databases with Ansible
  15. 15. Route 53 DNS Automation
  16. 16. CloudWatch Monitoring and Alarms
  17. 17. Managing Secrets: Secrets Manager, SSM Parameter Store and Ansible Vault
  18. 18. Post-Provisioning Configuration with Roles
  19. 19. Bridging Provisioning and Configuration: add_host and wait_for
  20. 20. Auto Scaling Groups and Rolling Updates
  21. 21. Validating Infrastructure with Assertions and Health Checks
  22. 22. Error Handling and Rollback in AWS Playbooks
  23. 23. Structuring a Reusable AWS Automation Project
  24. 24. Cost Control and Teardown Playbooks
  25. 25. Capstone: Provision and Configure a Multi-Tier AWS Application
View path overview →

google.cloud 1.14.0 - Whats New and How to Test

Introduction

google.cloud is the Ansible collection that provides modules and plugins for managing Google Cloud Platform resources, including Compute Engine, Cloud Storage, IAM, AlloyDB, Cloud Build, Colab, and Vertex AI. Version 1.14.0 has just landed on Ansible Galaxy, and this post covers exactly what changed and how to install and verify it.

Whats New

This release is a minor version bump and, based on the collection's own changelog, contains a single change: several groups of modules have been migrated to a shared, updated module_utils base.

Minor Changes

  • gcp_alloydb_*, gcp_cloudbuild_*, gcp_colab_*, gcp_vertexai_* modules now use plugins/module_utils/gcp_v2.py instead of their previous module_utils implementation (PR #763).

This is an internal refactor rather than a behavioral or interface change for playbook authors. The affected module families are:

Module familyResource area
gcp_alloydb_*AlloyDB clusters and instances
gcp_cloudbuild_*Cloud Build triggers and workers
gcp_colab_*Vertex AI Colab Enterprise runtimes
gcp_vertexai_*Vertex AI endpoints, models, and datasets

Consolidating these modules onto gcp_v2.py brings them in line with the newer GCP module_utils pattern already used elsewhere in the collection, which should make future maintenance and bugfixes across these four resource families more consistent.

No other minor changes, bugfixes, or breaking changes are listed in the changelog for this version.

How to Install and Test

# Install (or upgrade to) google.cloud 1.14.0
ansible-galaxy collection install google.cloud:1.14.0 --force

# Verify the installed version
ansible-galaxy collection list google.cloud

# Inspect the changelog shipped with the collection
find ~/.ansible/collections/ansible_collections/google/cloud -iname "CHANGELOG.rst"

# Quick sanity check on one of the affected modules
ansible-doc google.cloud.gcp_vertexai_endpoint

If the required Python dependencies (google-auth, requests) are not already present, install them before running any playbooks against real GCP resources:

pip install google-auth requests

As always, run any AlloyDB, Cloud Build, Colab, or Vertex AI playbooks in check mode first (--check --diff) against a non-production project to confirm the module_utils migration has not introduced any unexpected behavior in your environment.

All Tutorials