-
Type:
New Feature
-
Status: Resolved
-
Priority:
Normal
-
Resolution: Fixed
-
Affects Version/s: PUP 6.11.0
-
Fix Version/s: PUP 5.5.20, PUP 6.15.0
-
Component/s: Types and Providers
-
Labels:
-
Environment:
CentOS 8, RHEL 8 agents.
-
Template:customfield_10700 342086
-
Agent OS:Other
-
Team:Night's Watch
-
Story Points:2
-
Sprint:NW - 2020-04-01, NW - 2020-04-15
-
Release Notes:Enhancement
-
Release Notes Summary:Support enabling DNF modules, in addition to installing them. This is done by default on modules with no default installation profile. Modules with profiles can be enabled by setting the `enable_only` parameter to `true` in the manifest.
-
QA Risk Assessment:Needs Assessment
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.
- relates to
-
-
- Resolved
-
