heat-templates/hot/software-config/example-templates/config-scripts/example-script.sh

#!/bin/sh -x
echo "Writing to /tmp/$bar"
echo $foo > /tmp/$bar
echo -n "The file /tmp/$bar contains `cat /tmp/$bar` for server $deploy_server_id during $deploy_action" > $heat_outputs_path.result
echo "Written to /tmp/$bar"
echo "Output to stderr" 1>&2
Software config hook to provision using shell scripts Deployment input values are mapped to shell environment variables. Scripts can write output values to $heat_outputs_path.{output_name} These output values will be signalled back to heat, making these values available to the stack, and placing that deployment resource in a COMPLETE state. The example template demonstrates deploying a single config with more that one deployment resource, each with different input values. The only reason this is the first hook to be authored is because a script is a "configuration tool" which requires no tooling to set up. Closes-Bug: #1279064 Change-Id: Ib297957ad0f89e34b7930ba97886116bff1e313c 2014-04-03 13:50:43 +13:00			`#!/bin/sh -x`
			`echo "Writing to /tmp/$bar"`
			`echo $foo > /tmp/$bar`
			echo -n "The file /tmp/$bar contains `cat /tmp/$bar` for server $deploy_server_id during $deploy_action" > $heat_outputs_path.result
			`echo "Written to /tmp/$bar"`
			`echo "Output to stderr" 1>&2`