Tips¶
Running System Tests¶
claw generate
and claw bootstrap
create a symlink to the last generated
configuration directory in $CLAW_HOME/configurations/_
.
With this in place, instead of exporting the HANDLER_CONFIGURATION
environment variable every time you run a system test, to some other
handler-configuration.yaml
file, you can export this hard coded environment
variable:
export HANDLER_CONFIGURATION=PATH_TO_CLAW_HOME/configurations/_/handler-configuration.yaml
Remember that claw bootstrap
will update handler-configuration.yaml
with the manager_ip
of the newly bootstrapped manager.
Current Configuration¶
As mentioned in the previous section, the last generated/bootstrapped
configuration will always be symlinked at $CLAW_HOME/configurations/_
.
As such, you can save some more typing by using _
instead of the
configuration name, in all commands that take the configuration name as their
first argument.
For example, if we recently bootstrapped an environment based on a handler
configuration named datacentred_openstack
, and we wish to run some script
with the datacentred_openstack
environment as the script’s cosmo
,
instead of writing:
$ claw script datacentred_openstack my_script
we can instead write:
$ claw script _ my_script
to get the same result. Much shorter.