Hi,
I'm setting up a puppetserver that will be shared by multiple projects and
would like to enforce some control over access to environment resources -
particularly puppet:///modules/... file server URLs.
The environment name appears at the start of the URL, so with an
Apache/Passenger setup
As of 3.1 this functionality has been deprecated and replaced by 'future
parser' in 3.2.
See release notes for full detail.
https://puppetlabs.com/blog/puppet-3-2-introduces-an-experimental-parser-and-new-iteration-features
HTH
Den
> On 14 Mar 2015, at 19:05, spare.sl...@gmail.com wrote:
>
>
Hi,
According to official Puppet documenttion:
https://docs.puppetlabs.com/guides/faq.html#why-does-puppet-have-its-own-language
As for just using Ruby as the input format, Puppet 2.6.0 actually added
> this functionality, and manifests can now be written in pure Ruby. However,
> this capabili
Hi Chris, there are a few different resources, depending on what
language and what specific resources you're interested in.
We now have many of the docs on the main puppetlabs documentation site
available in Spanish: http://docs.puppetlabs.com/es/
There's an active Brasilian puppet user group w
I would suggest taking a step back - why do you have a requirement to read
the list of packages from a file?
On Friday, March 13, 2015 at 10:15:07 PM UTC+11, Alex Miroshnik wrote:
>
> Hi Guys,
>
> I need to install multiple packages on the Ubuntu 14.0.4 using puppet. All
> packages are listed i
You have declared a property ip. This means that it will be ensurable as
well and you should declare setter and getter for it:
def ip=(newip)
# Mayby like this
host = resource[:name]
postdata = {
'addr' => newip,
'hostnames' => [ host ]
}
RestClient.put("#{baseurl}#
On Saturday, March 14, 2015 at 2:02:47 AM UTC+13, jcbollinger wrote:
>
>
>
> On Friday, March 13, 2015 at 2:54:56 AM UTC-5, lupin...@gmail.com wrote:
>>
>> Hi,
>>
>> I'm on my first attempt of writing a custom type/provider and hope to
>> learn on the process. I'm got a stumbling block and lost
