Pass job/instance/label value context to scripted checks

[peterschretlen]

What would you like to be added:

(logging on behalf of a customer)

Some synthetic scripts can be repurposed to run in multiple environments, like testing environment or production.
The targets for these environments might be different URLs and have different credentials for login, but otherwise the scripts are identical.

The request is to be able to pass data like

• jobname
• instance
• label values to the script as context.

This would allow the instance value to be used as the starting or base url for example. a label value like env=test or env=prod can be used to determine which set of credentials are used. The script would have some idea of the context that it's running in.

Why is this needed:

Right now the only option ( I can see ) is to pre-bundle the scripts with environment-specific values and/or make environment specific scripts.

[peterschretlen]

Alternative could be to allow setting key-value pairs and passing these as environment variables to scripts.