You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I discussed this at length in Puppet Slack, with ideas ranging from implementing stuff in Puppet core, puppet-yum module and a dedicated module. We ended up agreeing in managing profiles (un)installation in core package type (which is the official (un)installer), requiring the changes proposed in this report, and moving DNF streams management (which is a configuration, not an (un)installation) to puppet-yum module. I'm still open to ideas.
The text was updated successfully, but these errors were encountered:
dnfmodule provider can (un)install DNF profiles. But it has some limitations:
dnfmodule
provider - profiles, instead of packagesSo I'd like to propose, and try to implement, these changes:
flavor
parameter accept arrays, so to (un)install multiple profilesensure
* - as opposed toinstalled
,absent
,latest
, and so ondnfmodule
provider so to make all functioning clear* puppet-yum module will soon support full DNS stream management, so this could be deprecated altogether from
dnfmodule
providerI discussed this at length in Puppet Slack, with ideas ranging from implementing stuff in Puppet core, puppet-yum module and a dedicated module. We ended up agreeing in managing profiles (un)installation in core
package
type (which is the official (un)installer), requiring the changes proposed in this report, and moving DNF streams management (which is a configuration, not an (un)installation) to puppet-yum module. I'm still open to ideas.The text was updated successfully, but these errors were encountered: