On Wed, Oct 12, 2011 at 2:20 PM, Gonzalo Servat wrote:
> On Thu, Oct 13, 2011 at 2:25 AM, Nigel Kersten wrote:
>
>>
>> Are you saying you're sourcing files from outside the current environment
>> for the client?
>>
>> if you put your files into modules that differ per environment, then
>> somethi
On Thu, Oct 13, 2011 at 2:25 AM, Nigel Kersten wrote:
>
> Are you saying you're sourcing files from outside the current environment
> for the client?
>
> if you put your files into modules that differ per environment, then
> something like:
>
> puppet:///modules/mymodule/myfile
>
> will resolve t
On Wed, Oct 12, 2011 at 7:02 PM, Daniel Maher wrote:
> On 10/11/2011 11:14 PM, Gonzalo Servat wrote:
>
> I am re-doing the Puppet config and trying to come up with a better way
>> of solving the multiple environment problem. Sometimes files need to be
>> sourced that depend on their environment.
On Tue, Oct 11, 2011 at 2:14 PM, Gonzalo Servat wrote:
> Hi All,
>
> In our environment, we have production and DR puppet clients that live on
> different networks. Currently, we do things like "include s_service::prod"
> or "include s_service::dr", etc. Both of these subclasses would inherit fro
On 10/11/2011 11:14 PM, Gonzalo Servat wrote:
I am re-doing the Puppet config and trying to come up with a better way
of solving the multiple environment problem. Sometimes files need to be
sourced that depend on their environment. Currently we do "source =>
puppet:///${env}/file", which isn't v
Hi All,
In our environment, we have production and DR puppet clients that live on
different networks. Currently, we do things like "include s_service::prod"
or "include s_service::dr", etc. Both of these subclasses would inherit from
s_service where common things lie.
I am re-doing the Puppet con
