As per Collections Removal Process — 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 was filed eight months ago with no response from the collection maintainers after multiple pings.
Vote: Should google.cloud be removed from Ansible 12?
Steering Committee Vote
- Yes
- No
0
voters
Community Vote
- Yes
- No
0
voters
The vote has passed. We now need to add the removal: entry to the metadata in ansible-build-data.
1 Like
For the record: Remove google.cloud from Ansible 12
1 Like
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
In particular, note:
This does fix all of the issues in
validate-modules, which is what #613 is specifically about.
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.
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? and the resulting discussion/vote [Vote ended on 2023-02-14] Unmaintained collection: `google.cloud` · Issue #105 · ansible-community/community-topics · GitHub; 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) 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 for the process - I guess it’s missing step 0 “Someone needs to request that it gets re-added” though).
1 Like
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?
It does affect the documentation on Ansible Documentation — Ansible Community Documentation, 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.
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
1 Like
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.
1 Like
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…?
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.)
@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).
Good point! Maybe we should wait with canceling the removal until Test with ansible-core 2.19 (or something similar) has been merged 
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.
- Ansible Y has not yet been released.
- All the requirements violations have been fixed.
Seems like these two requirements have been met, so we we can keep the collection
@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 
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:
Steering Committee vote
- Cancel google.cloud removal from Ansible 12
- Remove google.cloud from Ansible 12
0
voters
Community vote
- Cancel google.cloud removal from Ansible 12
- Remove google.cloud from Ansible 12
0
voters