-
Notifications
You must be signed in to change notification settings - Fork 342
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
ipv4, ipv6, ipsubnet have moved from ansible.netcommon to ansible.utils #635
ipv4, ipv6, ipsubnet have moved from ansible.netcommon to ansible.utils #635
Conversation
Build succeeded.
|
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.
@sebastien-rosset Thank you for taking time to work on this. Could you please add a changelog fragment?
@alinabuzachis yes we should backport it so CI is working for that branch, thanks! |
Build succeeded (gate pipeline).
|
Backport to stable-2: 💚 backport PR created✅ Backport PR branch: Backported as #659 🤖 @patchback |
…ls (#635) ipv4, ipv6, ipsubnet have moved from ansible.netcommon to ansible.utils SUMMARY This is a maintenance task to migrate from ansible.netcommon to ansible.utils. I was trying to fix an issue in that module, but I was told the functions have moved to ansible.utils. See ansible-collections/ansible.netcommon#362 (comment) ISSUE TYPE Bugfix Pull Request COMPONENT NAME Existing integration tests that use the ansible.netcommon module. No module uses netcommon, only integration tests. ADDITIONAL INFORMATION Reviewed-by: Alina Buzachis <None> (cherry picked from commit 0db6ac1)
Backport to stable-3: 💚 backport PR created✅ Backport PR branch: Backported as #661 🤖 @patchback |
…ls (#635) ipv4, ipv6, ipsubnet have moved from ansible.netcommon to ansible.utils SUMMARY This is a maintenance task to migrate from ansible.netcommon to ansible.utils. I was trying to fix an issue in that module, but I was told the functions have moved to ansible.utils. See ansible-collections/ansible.netcommon#362 (comment) ISSUE TYPE Bugfix Pull Request COMPONENT NAME Existing integration tests that use the ansible.netcommon module. No module uses netcommon, only integration tests. ADDITIONAL INFORMATION Reviewed-by: Alina Buzachis <None> (cherry picked from commit 0db6ac1)
…ls (#635) (#661) [PR #635/0db6ac10 backport][stable-3] ipv4, ipv6, ipsubnet have moved from ansible.netcommon to ansible.utils This is a backport of PR #635 as merged into main (0db6ac1). SUMMARY This is a maintenance task to migrate from ansible.netcommon to ansible.utils. I was trying to fix an issue in that module, but I was told the functions have moved to ansible.utils. See ansible-collections/ansible.netcommon#362 (comment) ISSUE TYPE Bugfix Pull Request COMPONENT NAME Existing integration tests that use the ansible.netcommon module. No module uses netcommon, only integration tests. ADDITIONAL INFORMATION
…ls (#635) (#659) [PR #635/0db6ac10 backport][stable-2] ipv4, ipv6, ipsubnet have moved from ansible.netcommon to ansible.utils This is a backport of PR #635 as merged into main (0db6ac1). SUMMARY This is a maintenance task to migrate from ansible.netcommon to ansible.utils. I was trying to fix an issue in that module, but I was told the functions have moved to ansible.utils. See ansible-collections/ansible.netcommon#362 (comment) ISSUE TYPE Bugfix Pull Request COMPONENT NAME Existing integration tests that use the ansible.netcommon module. No module uses netcommon, only integration tests. ADDITIONAL INFORMATION
…templates Add Issue Templates/Forms SUMMARY We've had a number of issues posted recently without the templates. This results in maintainers needing to guess to fill in the blanks. Use forms rather than the default template to make it harder to skip things like examples. ISSUE TYPE Feature Pull Request COMPONENT NAME .github ADDITIONAL INFORMATION Based on ansible-collections#400 and ansible-collections#401 Reviewed-by: Alina Buzachis <None>
SUMMARY
This is a maintenance task to migrate from ansible.netcommon to ansible.utils. I was trying to fix an issue in that module, but I was told the functions have moved to ansible.utils. See ansible-collections/ansible.netcommon#362 (comment)
ISSUE TYPE
COMPONENT NAME
Existing integration tests that use the ansible.netcommon module. No module uses netcommon, only integration tests.
ADDITIONAL INFORMATION