community.network
community.network copied to clipboard
avi modules migration
SUMMARY
Migrate the avi modules to the vmware.alb namespace
ISSUE TYPE
- Feature 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 migrate the modules in community.network over to the new collection. I tried to follow the Cisco PR (#142) but please let me know if there is anything that I am missing or needs to be corrected.
Since this content is part of the ansible
PyPI package, this PR cannot be merged as-is. There are two possible ways of moving forward:
- Get the
vmware.alb
collection included in theansible
package and then use the redirects to point to the new content. - Deprecate the existing content now and add redirects at removal time. The content can then probably be removed in Ansible 6.
But this definitely needs some community feedback.
@tadeboro when the content is deprecated, we cannot add redirects until the point of removal, since redirects would break existing users now.
@tadeboro when the content is deprecated, we cannot add redirects until the point of removal, since redirects would break existing users now.
Grr, I misplaced the now in my previous comment. Now things should read better.
@amolopcito This PR was evaluated as a potentially problematic PR for the following reasons:
- More than 50 changed files.
Such PR can only be merged by human. Contact a Core team member to review this PR on IRC: #ansible-devel
on Libera.chat IRC