From 7748ff3123dc4a3b6f0b5c5956a00f1d5bb285f4 Mon Sep 17 00:00:00 2001
From: Dan Guido <dan@trailofbits.com>
Date: Fri, 8 May 2026 13:55:40 -0400
Subject: [PATCH] Declare missing cloud collections in requirements.yml
 (#15000)

Four cloud roles use modules from collections that were not declared in
requirements.yml: cloud-ec2 and cloud-lightsail use cloudformation and
ec2_ami_info from amazon.aws, cloud-gce uses gcp_compute_* from
google.cloud, cloud-hetzner uses hetzner.hcloud.server and ssh_key, and
cloud-cloudstack uses cs_instance, cs_securitygroup, and cs_securitygroup_rule
from ngine_io.cloudstack. Deploys to these providers worked only when the
collections happened to be installed from another source. On a fresh
install via ansible-galaxy install -r requirements.yml, the roles would
fail at runtime with module-not-found errors.

This is the same bug class as #14999 (vultr.cloud).
---
 requirements.yml | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/requirements.yml b/requirements.yml
index e489a160..a017bc28 100644
--- a/requirements.yml
+++ b/requirements.yml
@@ -18,3 +18,11 @@ collections:
     version: ">=3.0.0"
   - name: vultr.cloud
     version: "==1.14.0"
+  - name: amazon.aws
+    version: "==10.3.1"
+  - name: google.cloud
+    version: "==1.13.0"
+  - name: hetzner.hcloud
+    version: "==6.9.0"
+  - name: ngine_io.cloudstack
+    version: "==3.0.0"