[New Standard]: On-demand Scripts #22
Description
What new standard is being proposed?
Specification of on-demand script directory, e.g., pkghome/ush/on-demand to contain scripts that are run "on-demand" (i.e., designed to be run "stand-alone", and not designed to be called by the usual job_card(j_job(ex_script(ush))) composition).
Why is the new standard necessary?
Existing standards do not allow exceptions for on-demand scripts which will break many existing standards (specifying hard-coded paths in a ush script, sourcing run.ver in a ush script, etc.).
Devs and Ops need a means by which to identify "on-demand" scripts and therefore treat them differently re: standards compliance.
How will the new standard be enforced?
All on-demand scripts shall either be named with on-demand in the file name or be located within a designated and easily recognized directory, e.g., pkghome/ush/on-demand/
Impact of this standard?
Devs and ops will be affected.
Little effort to adopt, but effort required to update and organize standards in a way to make this exception clear.
No need to update existing code; all existing on-demand scripts are already out of compliance with existing EE2 standards.
No operational risk. T2O risk can be mitigated by making this change to the standards easily seen.