Am Sonntag, den 07.04.2019, 05:47 -0700 schrieb KRouth Clinipace:
Know i will see the other options proposed here
puppetlabs::stdlib -> file_line
Why reinvent the wheel?
Bye...
Dirk
--
Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226
It looks like what you're trying to do is inline editing of /etc/bashrc,
but still let people poke at it themselves. That's a fragile position to be
in. For example, given your regex solution, what's to stop someone from
doing something like innocently defining their $PS1 iteratively? Something
lik
On 2019-04-07 14:47, KRouth Clinipace wrote:
Question - is it possible to use the puppet regsubst function in place
of the exec used here (to save spawning a new shell process) ?
kevin
Well, functions are ordinary on the compiling side. If you can figure
out what to do when compiling that is
Question - is it possible to use the puppet regsubst function in place of
the exec used here (to save spawning a new shell process) ?
kevin
On Friday, May 21, 2010 at 10:28:58 PM UTC-4, Marley Bacelar wrote:
>
> Nice... I solved my probleman using the:
>
> define replace($file, $pattern, $repla
I've moved my configuration as you suggested, and errors are starting to
populate my log, which is good!, because I wasn't getting error messages at
all.
I'm aware that my setup is monolithic and shoud be splitting my class
hierarchy into several files, but that would make my admin much more
c
