This feature allows setting a comman separated list of environment qualifiers in the 'nv.robin.env.qualifiers' environment variable. When set the Robin controller will look for locationN.<qualifier>.env environment property files for localizing the environment. This feature allows the localization of an environment to be augmented during deployment.

For example consider a location1.env for a given scenario:

When the scenario will be deployed to both QA and PROD environments, one could bundle a location1.qa.env and a location1.prod.env and set nv.robin.env.qualifiers to localize the scenario accordingly.

This story updates robin scripting to operate with the enhanced Command annotions introduced in Core X (see . It includes the following minor changes that support the server side command argument processing:

• instruct, wait and validate commands were enhanced to allow quoting command arguments to allow string arguments with embedded spaces
• wait and validate commands were enhanced to allow checking against the new primitive return types that commands may now return

• wait and validate now interpret true and false response as success and failure respectively in the absense of an explicit value to wait for.

  CONTROLLER

This resolves an issue in programmatic Robin Controller close in which admin connections to made to running Servers were not being closed. This would cause heartbeats to continue to be received after a controller's model is closed.

Fixes an issue with the robin collect script command not generating a unique run id. The collect command saves results to a path given by:

<scenario-dir>/results/<run-qualifier>/<run-id>/<identifier>

When a script is loaded a unique run-id should be set to a timestamp value to ensure that results end up in a unique folder but instead a value of null was being inserted. This change resolves this issue. Users that need to preserve the old behavior may set the environment variable nv.robin.controller.run.id=null.

Fixes the behavior of the variant of the robin scripting wait command that waits for the return value to match that of the script:

wait until <appName> app in the <serverName> server <command> is <value> [with <params>]

Prior to this fix the wait command would errornously break from waiting even if the wait condition was not met. The command now has the following semantics:

• Waits until the command's return value matches that specified
• If an exception is thrown from the command the wait command fails

• Otherwise the the script will continue executing the command at 5 second intervals until the wait condition is met.

  CONTROLLER