Puppet users - Apr 2013 - Managing "<Directory>" entries in httpd.conf with Puppet.

So I am working on deploying Puppet for our environment, and I have hit a 
snag. We have a few applications hosted on Apache, each with different 
"<Directory>" entries. There is no way to standardize them
across all of
our application pools and they often overlap. I know I can have a custom 
template for each type of application, but it would be nice to make it as 
generic as possible. 

How do you manage multiple "<Directory>" tags in httpd.conf via
Puppet?
 

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

You don''t

You''d manage a static httpd.conf which includes from a conf.d directory
containing site-specific configs. At the end of the day you want a define 
that allows you do work like this psuedo code:

http:site { 
  thisawesomesiteisenabledbydefault:;
  thisisold: ensure => absent;
}

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Simple answer: don''t. Use apache''s conf.d construct to manage
virtual hosts
for each so they can contain their own config. See the puppetlabs apache 
module:

https://github.com/puppetlabs/puppetlabs-apache

On Wednesday, April 3, 2013 10:57:30 AM UTC-6, Cesar Covarrubias
wrote:
>
> So I am working on deploying Puppet for our environment, and I have hit a 
> snag. We have a few applications hosted on Apache, each with different 
> "<Directory>" entries. There is no way to standardize them
across all of
> our application pools and they often overlap. I know I can have a custom 
> template for each type of application, but it would be nice to make it as 
> generic as possible. 
>
> How do you manage multiple "<Directory>" tags in httpd.conf
via Puppet?
>  
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.