I'm trying to get a useful tool for our operations guys, to give them some
transparency on compiled values for a node.
The theory is they could put their hieradata code in on a feature branch,
and I could give them a report of all the values that would go into that
node, and also show values t
did you check your puppet.conf at your agent ?
maybe you [agent]
environment = devops
try
environment = production
i saw the error message on my text box when i mess around the testing, i
fixed if i change it to production, hope it helps.
On Thursday, October 30, 2014 at 7:21:48 AM UTC-7, Da
On Wednesday, January 28, 2015 at 9:45:04 AM UTC-5, jcbollinger wrote:
>
>
>
> On Tuesday, January 27, 2015 at 9:36:35 AM UTC-6, Dave Jablonski wrote:
>>
>> I am trying to generate separate jndi.xml files for a mule_config module
>> I'm building. Current setup:
>>
>>
>
> Much of what you say se
Hi Laxmi,
I could not find a way out to add multiple lines. I did this, which served
my purpose. May be it is not suitable for your requirement.
file { "/etc/mytweaks":
owner => 'root',
group => 'root',
mode=> '0755',
source => "puppet:///modules/tweaks-histo
On Tuesday, August 12, 2014 at 1:57:14 AM UTC-5, Vikas Kumar wrote:
>
> Hello,
>
> I am looking for an option to add multiple lines to a */etc/bashrc* and
> */etc/profile*. I can do this with *file_line*, but is there any other
> alternative. *file_line* does the job but for each line I will ha
On Tuesday, January 27, 2015 at 9:36:35 AM UTC-6, Dave Jablonski wrote:
>
> I am trying to generate separate jndi.xml files for a mule_config module
> I'm building. Current setup:
>
>
Much of what you say seems quite reasonable, but bits of it are enough off
to make me scratch my head, starti
The way to think about getting commands to run during the apply phase is
either by using exec resource (which basically don't have a return value so
don't allow you to access the data you want) or with providers.
In your example, if you wrote a custom notify provider, then instead of
using the gen
