You might be better off using something like Puppet Bolt to deploy the file
as a one off task at provisioning, rather than trying to manage it
declaratively through Puppet.
On Fri, 29 Jan 2021, 3:50 pm Steve McKuhr, wrote:
> In an effort to avoid errors triggered by validate_cmd, I ended up usin
In an effort to avoid errors triggered by validate_cmd, I ended up using
a conditional based on a File.exists custom fact. I'm still open to
suggestions, this is all new territory to me.
On Thu, 2021-01-28 at 17:13 -0800, Steve McKuhr wrote:
> I've just realized that my problem statement was s
I've just realized that my problem statement was slightly misleading. A
'users' file gets installed as part of the software package, and the
goal is replacing its contents during the first Puppet run. The next
Puppet runs should ignore any changes.
On Thu, 2021-01-28 at 20:07 +0100, Martin Al
and please use ensure => file !
this is more clear.
you can set the file ensure attribute to one of the following: file, directory,
link, absent
> On 28. Jan 2021, at 18:58, Ben Ford wrote:
>
> Yep, just use the replace attribute on the file resource.
> https://puppet.com/docs/puppet/latest/t
Yep, just use the replace attribute on the file resource.
https://puppet.com/docs/puppet/latest/types/file.html#file-attribute-replace
On Thu, Jan 28, 2021 at 9:57 AM Steve McKuhr wrote:
> I'd like to initialize a user config file once, at software install time,
> then allow application admins t
I'd like to initialize a user config file once, at software install time,
then allow application admins to manage the file contents via web interface
(add/remove users, etc.) - I have come up with the following:
file { 'users':
ensure => present,
content => template('my-template'),
validat
