Warn of unused environment variables in command #224
Description
Paint Point? Please describe.
When a user is constructing an job.interface.command we should be able to validate that all the environment variables they specify are actually provided by the system. This would go a long way to helping people who mistakenly use lowercase or other non-normalized characters in their command string.
Desired Solution
Issue a strongly worded warning indicating to the user that they have variables that are not recognized as either a reserved keyword or an input value. This should not prohibit them from continuing, but will ensure they are aware of the danger.
If they are using something like ${output_dir} or ${job_output_dir} it would also be nice to intelligently suggest that maybe they meant ${OUTPUT_DIR}.