-
Notifications
You must be signed in to change notification settings - Fork 90
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
[4.0.0] Drop Ansible 2.9 and ansible-base 2.10 compatibility #426
[4.0.0] Drop Ansible 2.9 and ansible-base 2.10 compatibility #426
Conversation
bot_skip |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks @felixfontein
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@felixfontein great job! LGTM
Follow-up PR in #428, needs this one to pass the (updated) tests. |
@Ompragash would you like to merge this one?:) |
Please don't forget that this needs to be merged and community.network 4.0.0 released by May 23rd :) |
Thanks, Andrei and Felix! I'll merge and close this. |
@Ompragash @Andersson007 thanks for reviewing and merging! |
SUMMARY
Similar to ansible-collections/community.general#4548 and ansible-collections/community.general#4562, officially drop compatibility for Ansible 2.9 and ansible-base 2.10 as announced in the changelog, and replace symlinks with runtime redirects.
ISSUE TYPE
COMPONENT NAME
collection