Skip to content
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

Use FQCN for builtin module actions (ansible.builtin.yum) #110

Open
paddyroddy opened this issue Jun 4, 2024 · 3 comments
Open

Use FQCN for builtin module actions (ansible.builtin.yum) #110

paddyroddy opened this issue Jun 4, 2024 · 3 comments
Labels
problem Something isn't working

Comments

@paddyroddy
Copy link
Member

paddyroddy commented Jun 4, 2024

Short Description

There seems to have been a recent Ansible lint change which recommends to:
Use ansible.builtin.dnforansible.legacy.dnf instead

Evidence/Steps to Reproduce

No response

Acceptance Criteria/Expected Behaviour

No response

Details

No response

Resolution

For now I've added to .ansible-lint

@paddyroddy paddyroddy added the problem Something isn't working label Jun 4, 2024
@p-j-smith
Copy link
Contributor

I think this is because yum is deprecated (and removed on latest versions of RHEL). ansible.builtin.yum uses yum on RHEL<8 and dnf otherwise. It looks like ansible.builtin.dnf will do the same, so we should be able to switch without any issues

@paddyroddy
Copy link
Member Author

@p-j-smith it's not as trivial as it seems. I tried this, and it was giving me warning about picking dnf4 or dnf5 which I wasn't too sure on. Then on top of this, we have a lot of hardcoded variables with yum in their title. Plus, things like rpm URLs may have changed.

@p-j-smith
Copy link
Contributor

ah I see, sounds like a lot more work then 😞

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants