Changes coming soon. Watch this space for updates on our new community.

Job-specific environment variables

jeff.keller
jeff.keller Member Posts: 9

It would be convenient to be able to specify job-specific environment variables when scheduling a job or running an ad hoc job. This would avoid the need to set project-level environment variables--even temporarily--as it might impact other project workloads that are not expecting the presence or value of the job-specific environment variable.

These new environment variables could be specified in the "Start a Job" and "Create a Scheduled Job" modals (attached).

An alternative, simpler, and less secure option would be to support commands that include in-line environment variables, for example:

MY_VAR="Hello World!" run.sh

This currently does not work because Domino's interpreter detection fails with a command like this. The ad hoc modal will return an error immediately, while the scheduling modal will accept the command, but will fail with the same error when the scheduled job starts.

Yes, an alternative would be to use command arguments like this:

run.sh --my_var="Hello World!"

But this requires setting up getopts, getopt, optparse, etc. infrastructure that could be unnecessarily complex for the needs of a quick ad hoc job. Command arguments are also not secure.


5 votes

Active · Last Updated

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!