[chef] Re: Community cookbook & SELinux Configuration

["Julian C. Dunn" < >]

On Wed, Jan 14, 2015 at 6:38 PM, Greg Barker 
<
 >
 wrote:
> What's the appropriate way to handle SELinux configuration for a Vagrantfile
> or .kitchen.yml that ships with a community cookbook?
>
> I updated the nexus cookbook to use a new base box in the Vagrantfile and
> now it will fail if you have recipe[nginx] on the run list, because the new
> base box has SELinux enabled.
>
> Is there a way to require the selinux cookbook as a dependency but only for
> Vagrant & Test Kitchen? I was thinking of using that to just disable SELinux
> but I wouldn't want it to be a mandatory dependency for everyone.

My personal opinion (as one of the maintainers of the bento project)
is to just use baseboxes that have SELinux in a permissive state
(enabled but not enforcing). That gives the greatest flexibility
whilst testing.

- Julian

-- 
[ Julian C. Dunn 
<
 >
          * Sorry, I'm    ]
[ WWW: http://www.aquezada.com/staff/julian    * only Web 1.0  ;]
[ gopher://sdf.org/1/users/keymaker/           * compliant!    ;]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9       ]