Jira (PUP-10235) Support enable module with dnfmodule package provider
Title: Message Title Jens Almer commented on PUP-10235 Re: Support enable module with dnfmodule package provider I missed your comment about the DNF behavior change. Good find! Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342086.157904321.22691.1585328220026%40Atlassian.JIRA.
Jira (PUP-10235) Support enable module with dnfmodule package provider
Title: Message Title Jens Almer commented on PUP-10235 Re: Support enable module with dnfmodule package provider Hey Gabriel, I appreciate your work on this! I never noticed the fallback behavior, but I can confirm that is correct. My assumption after observing the lack of idempotency was that it was failing to enable the module. The open PR should meet my needs. Takk! --Jens On Fri, Mar 27, 2020 at 6:28 AM Gabriel Nagy (Jira) < Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342086.157904321.22671.1585327380271%40Atlassian.JIRA.
Jira (PUP-10235) Support enable module with dnfmodule package provider
Title: Message Title Jens Almer created an issue Puppet / PUP-10235 Support enable module with dnfmodule package provider Issue Type: New Feature Affects Versions: PUP 6.11.0 Assignee: Unassigned Components: Types and Providers Created: 2020/01/14 3:06 PM Environment: CentOS 8, RHEL 8 agents. Priority: Normal Reporter: Jens Almer The dnfmodule package provider currently only supports installing a profile, ala `dnf module install module-name:stream/profile`. Some modules do not provide profiles, and can only be enabled. For example, the 389-ds module. To install, 2 steps are required: `dnf module enable 389-ds:1.4` `dnf install 389-ds-base` I think it would be ideal to allow for an 'enabled' value for the ensure parameter which would change the invocation of dnf. The stream should be passed in with a new or repurposed parameter. A secondary package resource can be used to install the needed package as that is not deterministic.
