Resources that use 'semanage' should have an autorequires on the various packages #345
Assignees
Comments
trevor-vaughan
added a commit
that referenced
this issue
May 19, 2021
Changed:
* Added `autorequire` calls to ensure that the necessary packages are
installed if `semanage` is to be used.
Closes #345
trevor-vaughan
added a commit
that referenced
this issue
May 20, 2021
Changed:
* Added `autorequire` calls to ensure that the necessary packages are
installed if `semanage` is to be used.
Closes #345
EmRowlands
pushed a commit
to EmRowlands/puppet-selinux
that referenced
this issue
Mar 29, 2023
Changed:
* Added `autorequire` calls to ensure that the necessary packages are
installed if `semanage` is to be used.
Closes voxpupuli#345
cegeka-jenkins
pushed a commit
to cegeka/puppet-selinux
that referenced
this issue
Jan 10, 2025
Changed:
* Added `autorequire` calls to ensure that the necessary packages are
installed if `semanage` is to be used.
Closes voxpupuli#345
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After using the latest release of the module, I noticed that
selinux_portwas having issues in some of my tests.This turned out to be that (for whatever reason) the package containing the python
semanagelibrary had not yet been installed.Instead of requiring users to include the entire module, I would like to propose that all commands that need
semanagehave anautorequiresadded on the various potential package names.Unfortunately, this means that a failure in a package update will cascade but this is pretty standard and will fix potential 'dual-run' issues moving forward.
The main drawback is that, as new OS flavors are added, the package list will need to be updated to reflect things. I don't think that requiring the
selinux::packageclass is a good idea because it contains more than the single package that is required for obtaining thesemanagecommand.The text was updated successfully, but these errors were encountered: