Should we enable SELinux for RHEL family integration tests #155
Labels
Feature Request
Enhancement to existing functionality or new functionality
hacktoberfest
An issue highlighted for the digital ocean Hacktoberfest Event
This cookbook should work with SELinux set to
enforcing
and does contain resources to make it play nice, so we should try to include integration tests that make sure these SELinux related resources run correctly (e.g. the service is started after moving the data or binlog directories).The question is: do we create additional suites for testing SELinux functionality and only include the RHEL family platforms, or do we make all RHEL family platforms SELinux enabled by default. I would be surprised if something worked with SELinux set to
enforcing
but did not work when set topermissive
, but we are likely to see breakage when vice versa.Any feedback welcome as I'm torn between what to do.
The text was updated successfully, but these errors were encountered: