Removal of avi modules from community.network

[chandanapatnala]

SUMMARY

Remove the avi modules from community.network

ISSUE TYPE

• Removal Pull Request

COMPONENT NAME

• avi_actiongroupconfig
• avi_alertconfig
• avi_alertemailconfig
• avi_alertscriptconfig
• avi_alertsyslogconfig
• avi_analyticsprofile
• avi_api_session
• avi_api_version
• avi_applicationpersistenceprofile
• avi_applicationprofile
• avi_authprofile
• avi_autoscalelaunchconfig
• avi_backup
• avi_backupconfiguration
• avi_certificatemanagementprofile
• avi_cloud
• avi_cloudconnectoruser
• avi_cloudproperties
• avi_cluster
• avi_clusterclouddetails
• avi_controllerproperties
• avi_customipamdnsprofile
• avi_dnspolicy
• avi_errorpagebody
• avi_errorpageprofile
• avi_gslb
• avi_gslbgeodbprofile
• avi_gslbservice
• avi_gslbservice_patch_member
• avi_hardwaresecuritymodulegroup
• avi_healthmonitor
• avi_httppolicyset
• avi_ipaddrgroup
• avi_ipamdnsproviderprofile
• avi_l4policyset
• avi_microservicegroup
• avi_network
• avi_networkprofile
• avi_networksecuritypolicy
• avi_pkiprofile
• avi_pool
• avi_poolgroup
• avi_poolgroupdeploymentpolicy
• avi_prioritylabels
• avi_role
• avi_scheduler
• avi_seproperties
• avi_serverautoscalepolicy
• avi_serviceengine
• avi_serviceenginegroup
• avi_snmptrapprofile
• avi_sslkeyandcertificate
• avi_sslprofile
• avi_stringgroup
• avi_systemconfiguration
• avi_tenant
• avi_trafficcloneprofile
• avi_user
• avi_useraccount
• avi_useraccountprofile
• avi_virtualservice
• avi_vrfcontext
• avi_vsdatascriptset
• avi_vsvip
• avi_webhook

ADDITIONAL INFORMATION

The new collection is active on Galaxy here: https://galaxy.ansible.com/vmware/alb and on Github: https://github.com/vmware/ansible-collection-alb. This PR is to remove the avi modules from community.network.

[chaitanyaavi]

+1

[Andersson007]

@chandanapatnala hello, thank you for the PR
The content is currently a part of the Ansible package, so I have several related questions:

1. did you follow https://docs.ansible.com/ansible/devel/dev_guide/developing_collections_migrating.html#migrating-ansible-content-to-a-different-collection when moving content? @felixfontein could you please take a look? I think the modules first should be deprecated and then, in the next major release, the content should be actually removed.
2. your new collection will be a part of the Ansible package, so it must satisfy the Collection checklist (here's also its longer more detailed version). For example, i don't see the collection follows SemVer; all the other stuff should be checked as well.
   If you don't want your collection be a part of the package let us know.

[felixfontein]

Right now the current stance of the Steering Committee (SC) is that no modules can be migrated to collections that are not part of the Ansible package. This is something we can discuss on changing, but that needs discussion and approval by the SC first. As long as that decision stands, either your collection is added to Ansible first and then the plugins are moved, or the plugins are deprecated and then tombstoned (i.e. no redirects to your collection) in this collection.

So do you plan to submit your collection for inclusion in Ansible anyway (in which case let's do that first)? If not, we should start a discussion on whether we want to change the rule (https://github.com/ansible-community/community-topics/).

[felixfontein]

I created a community discussion in ansible-community/community-topics#167.

[chandanapatnala]

Hi. According to the discussion as the redirection to the new collection is added in this pr-

community.network/meta/runtime.yml

Line 527 in f242b60

avi_actiongroupconfig:

, can this pr be merged?

[felixfontein]

The discussion hasn't been concluded, so no.

[chandanapatnala]

@felixfontein Hi , Is there any conclusion to the discussion ?

[chandanapatnala]

@felixfontein Hi , Is there any conclusion to the discussion ? If yes , then I'll resolve the conflicts so that this pr can be merged

[felixfontein]

There is not. @ansible-collections/steering-committee a small reminder that ansible-community/community-topics#167 really needs to be discussed.

[felixfontein]

We finally got a decision on this (https://forum.ansible.com/t/5738/13): moving these modules to a collection outside of Ansible is now allowed under some specific conditions, which you can find here: https://github.com/ansible/ansible-documentation/pull/1971/files#diff-17918ba4d47cb68e11b669412c5ea11b87bd8b5944b04720c6b74d104c692829R477

If these conditions apply to vmware.alb, feel free to update this PR.