What should be done for the sorry state of the google.cloud collection?

Archives Ansible Project
1

Hello,

The google.cloud collection:

  • had only one commit the past 6 months
  • no release for almost 1.5 years
  • 90 open and completely unanswered issues
  • 26 pull requests ignored
  • does not support hundreds of APIs and operations for google cloud.

Also, ansible was removed from the magic modules repository because building it is no longer supported in that repo. That repo also had no ansible commits for a year.

Google has apparently no interest in the collection, Ansible people do not support, community is locked out.

My questions:

  • whom should users contact to resolve any of the above?
  • is the collection dead?
  • where is the appropriate place to discuss the above? ansible-community/community-topics?
2

Hi,

- had only one commit the past 6 months

there were actually two, and two more a bit more than 6 months ago. But
I know what you mean. Also a "bug fixes" commit which simply removes a
CI workflow and doesn't do anything else doesn't really count as a
useful change to the collection :slight_smile:

- whom should users contact to resolve any of the above?

I'm not sure who "owns" the collection (and its name).

- is the collection dead?

Looks like that to me.

- where is the appropriate place to discuss the above?
ansible-community/community-topics?

Yes, that's the place.

I guess it's a good first case for using the procedure we defined here:
https://github.com/ansible-collections/overview/blob/main/removal_from_ansible.rst#unmaintained-collections

Please create an issue with basically what you wrote in your email.

Cheers,
Felix

3

FYI, the collection is 'owned' by Google itself.

4

I opened an issue: https://github.com/ansible-community/community-topics/issues/105