[Puppet Users] Re: Why there is a need for the architecture fact when it is only using hardwaremodel fact?

2013-10-28 Thread beyonddc . storage
Got it, thank you very much On Friday, October 25, 2013 2:45:31 PM UTC-4, Daniele Sluijters wrote: Hi, It doesn't only use hardwaremodel fact: https://github.com/puppetlabs/facter/blob/master/lib/facter/architecture.rb#L6:L10 # Resolution: # On non-AIX IBM, OpenBSD, Linux and Debian's

[Puppet Users] inline_template private method `gets' called for false:FalseClass

2013-10-28 Thread beyonddc . storage
Hi, I am new to Ruby ERB and inline_template. Can anyone spot what's wrong with this inline_template? $moddedContent = inline_template(%= puts gets(nil).gsub(/one two three/,\\) /tmp/blah %) exec { /bin/echo '${moddedContent}' /tmp/blah : }

[Puppet Users] Why there is a need for the architecture fact when it is only using hardwaremodel fact?

2013-10-24 Thread beyonddc . storage
Hi all, hopefully this is a quick question. I would like to know why there is a need for the architecture fact when it is only using hardwaremodel fact? Thanks! -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group

[Puppet Users] Failed to execute a command using the exec resource on Windows

2013-10-02 Thread beyonddc . storage
I am having a difficult time to determine the cause of why my exec resource failed to execute a command on Windows. Here's the error message reproduced by the Puppet on the windows machine when I ran 'puppet agent --test'. Error: cmd.exe /c ruby -e File.open('c:\replace_me', 'w') { |f|

Re: [Puppet Users] Failed to execute a command using the exec resource on Windows

2013-10-02 Thread beyonddc . storage
It's the path, you are right. After I set it, it ran successfully. Thanks! On Wednesday, October 2, 2013 3:26:56 PM UTC-4, Fernando Torres wrote: Did you provide the path attribute in your exec resource? Some like that: exe {'execute pretty command': command = 'cmd.exe /c echo 'hello

[Puppet Users] Question on task deletion using scheduled_task

2013-06-05 Thread beyonddc . storage
I have a very simple scheduled_task resource defined. class delete_task { scheduled_task { 'testing123': name = test_task, ensure= absent, } } I created this test_task by hand using the Windows Task Scheduler GUI. When I use Puppet and apply my resource, the task

Re: [Puppet Users] Question on task deletion using scheduled_task

2013-06-05 Thread beyonddc . storage
Hi Josh, That's explained it. Thanks for your information David On Wednesday, June 5, 2013 6:08:27 PM UTC-4, Josh Cooper wrote: Hi David, On Wed, Jun 5, 2013 at 12:08 PM, beyonddc...@gmail.com javascript:wrote: I have a very simple scheduled_task resource defined. class delete_task {

[Puppet Users] scheduled_task created but didn't see task under 'Task Scheduler' GUI

2013-04-25 Thread beyonddc . storage
Hi All, I created a scheduled_task resource and applied it. Puppet claimed that it did added successfully but when I go into the 'Task Scheduler' GUI, no such task exist. When I delete the same scheduled_task, Puppet found it and deleted it. Deleting the same scheduled_task twice, Puppet

[Puppet Users] Re: scheduled_task created but didn't see task under 'Task Scheduler' GUI

2013-04-25 Thread beyonddc . storage
Nevermind, please ignore my post. I was looking at the wrong place, the task did added successfully. It was under the Task Scheduler Library. Thanks... On Thursday, April 25, 2013 10:00:52 AM UTC-4, beyonddc...@gmail.com wrote: Hi All, I created a scheduled_task resource and applied it.

[Puppet Users] Re: Dependency Cycle Question

2013-04-03 Thread beyonddc . storage
Hi John, Your explanation should be correct. I believe the registry_key is behaving like the file resource since I was able to replace the problem using a file resource instead. You are also correct that the registry_key has autorequire implemented. The registry_key resource is downloaded

[Puppet Users] Dependency Cycle Question

2013-04-02 Thread beyonddc . storage
Hi All, I am new to Puppet and have a question on dependency cycle. I am currently applying my resource directly using the command prompt on Windows 'puppet apply --noop init.pp'. When I try to test it, I encounter a dependency cycle error. Error: Could not apply complete catalog: Found 1