New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(PUP-10235) Support enabling DNF modules #8047
(PUP-10235) Support enabling DNF modules #8047
Conversation
CLA signed by all contributors. |
167aa75
to
03d59ff
Compare
03d59ff
to
e39cafb
Compare
Acceptance passing with: |
jenkins please test this on fedora30-64a,fedora31-64a,redhat5-64a,centos6-64a,centos6-32a,centos8-64a,redhat7-64a,redhat7-POWERa,redhat7-AARCH64a,redhat8-64a,redhatfips7-64a |
0331c14
to
786433e
Compare
Add an optional `enable_only` parameter to the package type. If set to `true` on a `dnfmodule` resource, it will cause the module to be enabled instead of installed. The flag cannot be set together with the `flavor` property, since they conflict. DNF modules that have no default profile (and cannot be installed) will be enabled by default, so there is no need to add `enable_only`. To enable a module that has a default profile, `enabled_only` has to be set.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tested on CentOS 8, works as expected
Add an optional
enable_only
parameter to the package type.If set to
true
on adnfmodule
resource, it will cause the moduleto be enabled instead of installed. The flag cannot be set together
with the
flavor
property, since they conflict.DNF modules that have no default profile (and cannot be installed)
will be enabled by default, so there is no need to add
enable_only
.To enable a module that has a default profile,
enabled_only
has tobe set.