# \[Vote ended on 2025-07-21\] Collection removal: google.cloud **URL:** \ **Category:** Project Discussions\ **Tags:** gcp, community-wg, collection-exclusion\ **Created:** [September 18, 2024, 11:50pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609 "2024-09-18T23:50:09Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![gotmax23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gotmax23/32/106_2.png) [@gotmax23](https://forum.ansible.com/u/gotmax23)\ **Post date:** [September 18, 2024, 11:50pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/1 "2024-09-18T23:50:09Z")
As per [Collections Removal Process — Collections not satisfying the Collection requirements](https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_package_removal.html#collections-not-satisfying-the-collection-requirements), google.cloud is subject to removal from Ansible 12 after failing to address policy violations. [(Removal from Ansible) Community package requirements: sanity tests · Issue #613 · ansible-collections/google.cloud · GitHub](https://github.com/ansible-collections/google.cloud/issues/613) was filed eight months ago with no response from the collection maintainers after multiple pings. ---
**Author:** ![gotmax23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gotmax23/32/106_2.png) [@gotmax23](https://forum.ansible.com/u/gotmax23)\ **Post date:** [September 30, 2024, 8:53pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/2 "2024-09-30T20:53:27Z")
**Vote** : Should `google.cloud` be removed from Ansible 12? _Poll ([view on site](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/2))_ _Poll ([view on site](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/2))_ ---
**Author:** ![gotmax23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gotmax23/32/106_2.png) [@gotmax23](https://forum.ansible.com/u/gotmax23)\ **Post date:** [October 9, 2024, 6:23pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/3 "2024-10-09T18:23:08Z")
The vote has passed. We now need to add the `removal:` entry to the metadata in ansible-build-data. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [October 21, 2024, 4:24pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/4 "2024-10-21T16:24:19Z")
For the record: [Remove google.cloud from Ansible 12](https://github.com/ansible-community/ansible-build-data/issues/476) ---
**Author:** ![rpavlik](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/rpavlik/32/7231_2.png) [@rpavlik](https://forum.ansible.com/u/rpavlik)\ **Post date:** [January 16, 2025, 5:35pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/5 "2025-01-16T17:35:40Z")
What is anticipated to be the workaround once this is removed? (Is nobody else using GCP with Ansible?) It does look like there were fixes to most if not all of the issues: [Fix errors reported by ansible-test sanity by SirGitsalot · Pull Request #655 · ansible-collections/google.cloud · GitHub](https://github.com/ansible-collections/google.cloud/pull/655) In particular, note: > This does fix all of the issues in `validate-modules`, which is what [#613](https://github.com/ansible-collections/google.cloud/issues/613) is specifically about. ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [January 16, 2025, 6:22pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/6 "2025-01-16T18:22:56Z")
You can always simply use `ansible-galaxy collection install google.cloud` to install the collection if you use the `ansible` community package. If you don’t use the `ansible` community package, you have to explicitly install collections anyway, so in that case there should be no difference. > Is nobody else using GCP with Ansible? People are, but google.cloud doesn’t seem to be a good collection for GCP users, see for example [Community version of google.cloud](https://forum.ansible.com/t/9684). Also the collection has a history of being unmaintained for some time, see [What should be done for the sorry state of the google.cloud collection?](https://forum.ansible.com/t/36648) and the resulting discussion/vote [[Vote ended on 2023-02-14] Unmaintained collection: `google.cloud` · Issue #105 · ansible-community/community-topics · GitHub](https://github.com/ansible-community/community-topics/issues/105); in the last discussion you will find that the collection was once scheduled for removal, but that removal was cancelled ([Re-add google.cloud to Ansible 8 by mariolenz · Pull Request #201 · ansible-community/ansible-build-data · GitHub](https://github.com/ansible-community/ansible-build-data/pull/201)) later since the collection was maintained again. Generally it is also possible to cancel the scheduled removal again (see [Ansible Community Package Collections Removal Process — Ansible Community Documentation](https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_package_removal.html#canceling-removal) for the process - I guess it’s missing step 0 “Someone needs to request that it gets re-added” though). ---
**Author:** ![rpavlik](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/rpavlik/32/7231_2.png) [@rpavlik](https://forum.ansible.com/u/rpavlik)\ **Post date:** [January 16, 2025, 8:27pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/7 "2025-01-16T20:27:13Z")
Ah, I didn’t realize it could still be manually installed that way. I thought it was going to be removed there, which is why I was so startled. Though, I suppose this also affects the docs as well, right? ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [January 16, 2025, 8:42pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/8 "2025-01-16T20:42:01Z")
It does affect the documentation on [Ansible Documentation — Ansible Community Documentation](https://docs.ansible.com/ansible/latest/), which are the docs for the Ansible community package (which will no longer contain the collection). It does not affect the documentation on [Ansible Galaxy](https://galaxy.ansible.com/ui/repo/published/google/cloud/docs/). ---
**Author:** ![rpavlik](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/rpavlik/32/7231_2.png) [@rpavlik](https://forum.ansible.com/u/rpavlik)\ **Post date:** [January 16, 2025, 10:20pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/9 "2025-01-16T22:20:53Z")
well that didn’t take me long, two days in and I’ve hit the “wait a minute, this isn’t always updating things properly…” issue ---
**Author:** ![Steve\_Fulmer](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/steve_fulmer/32/5356_2.png) [@Steve\_Fulmer](https://forum.ansible.com/u/Steve_Fulmer)\ **Post date:** [July 14, 2025, 11:14am UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/10 "2025-07-14T11:14:29Z")
Hello, We at Red Hat are working with GCP to now maintain the collection in the couple past months. We have a co-support program where we maintain and respond to issues and Google releases it. I request now that this collection does not get deprecated. We already have had 2 releases since June. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [July 14, 2025, 12:18pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/11 "2025-07-14T12:18:17Z")
I think the requirements violations have been addressed. Or did I overlook something? So I guess we should start a vote on [canceling the removal](https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_package_removal.html#canceling-removal)…? ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [July 14, 2025, 12:59pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/12 "2025-07-14T12:59:21Z")
If we want to cancel the removal, we’ll have to hurry up, as feature freeze for Ansible 12 is in a week. (And that’s only since ansible-core has been delayed twice; otherwise it would already be too late.) ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [July 14, 2025, 1:05pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/13 "2025-07-14T13:05:14Z")
@Steve_Fulmer btw, I noticed that CI does not test against `stable-2.19`, which is now a good idea (since `devel` got bumped to 2.20 recently). ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [July 14, 2025, 1:48pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/14 "2025-07-14T13:48:31Z")
Good point! Maybe we should wait with canceling the removal until [Test with ansible-core 2.19](https://github.com/ansible-collections/google.cloud/pull/695) (or something similar) has been merged 🤔 ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [July 14, 2025, 2:07pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/15 "2025-07-14T14:07:46Z")
Well, we either start the vote to cancel the removal now, or we are no longer talking about cancelling the removal, but re-adding the collection since the removal will be final by beginning of next week 🙂 Since the tests pass for `devel`, they should very likely also pass for `stable-2.19` (at the current point of time, since `devel` is still very similar to `stable-2.19`), so I don’t think we have to wait for that. ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [July 14, 2025, 2:40pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/16 "2025-07-14T14:40:58Z")
> **[Ansible Community Package Collections Removal Process — Ansible Community...](https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_package_removal.html#canceling-removal)** > 1. Ansible Y has not yet been released. > 2. All the requirements violations have been fixed. Seems like these two requirements have been met, so we we can keep the collection ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [July 14, 2025, 2:44pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/17 "2025-07-14T14:44:31Z")
@gundalow Look a little bit below this, it says SC votes on whether the result is acceptable. So I guess we should have a vote… which I’m working on just now 😉 ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [July 14, 2025, 2:48pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/18 "2025-07-14T14:48:51Z")
I’m afraid we don’t have much time to discuss this, since the feature freeze for Ansible 12 is near. So I want to open a vote now, in order to at least give people a week to react. It looks like the sanity tests are working now, so the requirements are met. Let’s vote on this, with an end date of 2025-07-21: _Poll ([view on site](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/18))_ _Poll ([view on site](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/18))_ ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [July 21, 2025, 2:01pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/19 "2025-07-21T14:01:16Z")
We’ve reached quorum, and 100% (9 SC members, 3 from the community) are in favor of canceling the removal. Thanks all for voting! ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [July 30, 2025, 5:07pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-07-21-collection-removal-google-cloud/8609/20 "2025-07-30T17:07:32Z")
@Steve_Fulmer It would be _really_ great if someone would work on [Test with ansible-core 2.19](https://github.com/ansible-collections/google.cloud/pull/695). Compatibility with ansible-core 2.19 is important for collections included in Ansible 12, since it’s based on it…