-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove collection runtime dependencies #354
Comments
Files identified in the description: If these files are inaccurate, please update the |
This comment has been minimized.
This comment has been minimized.
How I would proceed:
I guess the ansible.netcommon and ansible.posix dependencies shouldn't do random changes, so we can live with them. I'm somewhat worried over cisco.intersight and community.kubernetes. If we could get rid of the modules/plugins, that would be great ;-) I guess that the dependent collections don't want to take them? That would be especially helpful for the cisco.intersight dependency, in particular because it has been authored by Cisco themselves. For the kubevirt stuff, moving it to a dedicated collection might help if community.kubernetes doesn't want to have it. |
Looks like |
I've added a commit to vendor the ovirt.ovirt parts to #353. |
Agreed - I had forgot the facts rename to info. I'll do the same rename in the collection and all cisco.intersight content (modules and utils) can be pulled from core. |
#372 loosens the dependency on google.cloud: the |
@dsoper2 please CC me in the ansible/ansible PR which changes routing. |
I've added plugins/connection/oc.py to the list of plugins depending on community.kubernetes (#577). |
For the kubevirt modules, see ansible-collections/community.kubernetes#221. For |
With the plan in ansible-collections/overview#117 (comment) all dependencies will vanish! |
ansible.posix is no longer a runtime dependency! \o/ |
This also removes the dependency on community.kubernetes which fixes ansible-collections#354.
* Remove kubevirt and set up redirects to community.kubevirt This also removes the dependency on community.kubernetes which fixes #354. * Update changelogs/fragments/1317-kubevirt-migration-removal.yml Co-authored-by: Felix Fontein <felix@fontein.de> * Update changelogs/fragments/1317-kubevirt-migration-removal.yml Co-authored-by: Felix Fontein <felix@fontein.de> * Add missed redirects Co-authored-by: Felix Fontein <felix@fontein.de>
* Remove kubevirt and set up redirects to community.kubevirt This also removes the dependency on community.kubernetes which fixes ansible-collections/community.general#354. * Update changelogs/fragments/1317-kubevirt-migration-removal.yml Co-authored-by: Felix Fontein <felix@fontein.de> * Update changelogs/fragments/1317-kubevirt-migration-removal.yml Co-authored-by: Felix Fontein <felix@fontein.de> * Add missed redirects Co-authored-by: Felix Fontein <felix@fontein.de>
SUMMARY
While including other collections for tests is fine, including them for runtime is dangerous. Changes in other collections can randomly break things in this collection.
I want to track dependencies to other collections in this issue, with the aim of being able to eventually remove them.
navigate_hash
and classGcpSession
)validate_ip_address
,validate_ip_v6_address
)ismount
)IntersightModule
and constantintersight_argument_spec
next to docs fragmentcisco.intersight.intersight
)ISSUE TYPE
COMPONENT NAME
collection
ANSIBLE VERSION
devel
The text was updated successfully, but these errors were encountered: