As a user, I can manage consumers that use DNF package manager
With Pulp3 so far underway, and not including consumers at all, adding this to Pulp2 is unlikely. I think we should do two things:
1. Create a blog post describing an alternate set of tooling (like ansible) to manage consumers via.
2. In the docs announce that dnf support is not planned and link to the blog post as a workaround.
3. Close this after as WONTFIX
#3 Updated by bmbouter almost 4 years ago
I think this feature request should be closed as WONTFIX unless someone from the community wants to send a PR for it. Consumers have been removed entirely from Pulp3, so users are going to need to switch off of Pulp code for consumer management anyway.
We should announce a deprecation of consumer management features if it hasn't been done already. We should additionally state that dnf based consumer actions won't be added. We should give some other options as alternatives such as Ansible. You can easily maintain an Ansible inventory to perform consumer actions with Ansible like you did with Pulp.
#11 Updated by daviddavis over 3 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp:pulp|576dbc03c00bf599f451b29544c31d0d7b3bbd63.
#14 Updated by ttereshc over 3 years ago
Do we want to close this one as a WONTFIX? so it will be clear that we didn't add support for DNF. Is it ok from rel-eng standpoint?
I get that the docs and blog post were created and the docs should go into release. But for users it can be confusing that status of the story is "closed-current release", though it's only docs which say that it won't be fixed.
Please register to edit this issue