On Sep 27, 12:52 pm, Damien Bridges <damien3...@gmail.com> wrote:
> Hi All,
>
> Does anyone know how to add bash code to the exec resource? I was
> thinking I could add it to the command section. I thought I could run
> the code after I put the link command and options in. However, it
> didn't work. My bash code has 'if' statements with $ signs in it. I
> want to move block to a directory with its version so it can be sym
> linked to /block.
> move-block () {
> if [[ -s /block/block && ! -h /block ]]; then
> VERSION= /block/block -v | grep -oE
> "[0-9] {1,4}. [0-9] {1,3}. [0-9] {1,4}. [0-9] {1,4}"
> RENAMED_DIR=/block_$VERSION
> echo; echo "Moving System to
> $RENAMED_DIR"
> rm -rf $RENAMED_DIR
> mv /block $RENAMED_DIR
> fi
>
> Thanks in advance,
Use single quotes to delimit the command. This will inhibit Puppet
from performing variable interpolation within, and will prevent Puppet
from interpreting the embedded double quotes. Alternatively, you can
use a backslash (\) to quote Puppet metacharacters within a string,
just like in the shell.
With that said, I have to agree with Damien that a script of any
significant complexity ought to be written to a file on the client
system and executed that way. For example, use a File resource to
ensure your script present in /tmp, and run it via an Exec. Be sure
to set up a relationship between the File and Exec resources to ensure
that they are applied in the right order.
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
