Am 07.11.2017 um 02:10 schrieb Andrei Iacob:
> is there a way to configure a set of environment variables to be
> available to a Service resource similar to what Exec supports?
>
> Looking at the documentation this doesn't seem to fit (except probably
> from the Manifest attribute but still can't
In general, I'd say you would have to put the variables into a
configuration file for the service (via a template, or an augeas resource),
or if the service is managed by systemd, in the relevant '???.service' file.
On Tuesday, 7 November 2017 16:27:39 UTC+2, Andrei wrote:
>
> Hello,
> is there
We released Puppet agent 4.10.9 on Monday, Nov. 6. This is a bug-fix
release of Puppet agent that updates cURL to 7.56.1, updates its
certificate authority (CA) certificate bundle, and updates Ruby and
rubygems to address several security vulnerabilities.
This release of Puppet agent also contains
Hi all,
We deploy Ubuntu 14.04 and 16.04 instances in AWS and use cloud-init to
bootstrap them. Specifically we pass them user-data in 'cloud-config' yaml
format (one of the formats that cloud-init understands).
Now that we've migrated to Puppet 4.10+ I'm having trouble finding the
correct syn
On Monday, November 6, 2017 at 10:13:11 AM UTC-6, titlei...@gmail.com wrote:
>
> Hello,
>
> I'm very new to Puppet and trying to implement 2 very simple modules.
> Both of these modules should work independent of each other, but both will
> be run on the same host. They both require that open
Dear Puppet Enterprise Users,
Puppet Enterprise 2016.4.9, 2017.2.5, and 2017.3.2 are now available.
These are security and bugfix releases of Puppet Enterprise. All users of
Puppet Enterprise are encouraged to upgrade when possible to the newest
versions.
These releases include fixes to address
Hey,
Why not just create a symlink ?
Also you should open a bug report https://launchpad.net/cloud-init
Best regards,
Le 07/11/2017 à 18:04, Martijn a écrit :
Hi all,
We deploy Ubuntu 14.04 and 16.04 instances in AWS and use cloud-init
to bootstrap them. Specifically we pass them user-data
Am 07.11.2017 um 16:24 schrieb Peter Faller:
> or if the service is managed by systemd, in the relevant '???.service'
> file.
Or, if the service file is shipped as part of a distribution package, in
a '*.conf' file in the corresponding '???.service.d' directory (to be
created), to avoid messing w
