The native puppet types don't seem to have support for dnf modularity. How does the Sat6 team plan to implement modularity support with puppet under Satellite?
Could you specify scope you expect to be done?
Do you need any assistance or any particular changes in the DNF stack?
If not, would you be fine with closing this bug?
Closing as the scope is unclear.
Please reopen the bug if you have more information on what we're expected to deliver.
The upstream issue at https://tickets.puppetlabs.com/browse/PUP-9978 has been updated:
Resolution Fixed [ 1 ]
Release Notes Summary Puppet now supports managing DNF modules, which are groups of packages that represent an application, a language runtime, or any logical group.
Modules can be available in multiple streams, usually representing a major version of the software they include. Profiles are package subsets representing a specific use case of the module (these are handled by the flavor parameter of the package type).
Due to the significant difference between a package and a module, dnfmodule is an opt-in provider and should be explicitly specified in the manifest.
Release Notes New Feature [ 11408 ]
Status Ready for Merge [ 10002 ] Resolved [ 5 ]
Fix Version/s PUP 6.11.0 [ 32097 ]
Fix Version/s PUP 6.4.5 [ 32095 ]
Fix Version/s PUP 5.5.18 [ 32091 ]
William, since the upstream Puppet issue has been resolved, is there anything left to do on DNF side or is this resolved just by that?
The RFE will be resolved for the customer once Satellite's Puppet is rebased on a version of upstream Puppet that has the new feature. So rather than closing the bug I prefer it to be assigned to Satellite Engineering.