Section 1.2.1 discusses merging parameter definitions when the same parameter name appears in multiple templates. However, it doesn't address whether a parameter defined only in an Environment Template is accessible from the Job Template.
The current wording in §1.2 says:
parameterDefinitions — A list of the Job Parameters that are available within the Environment Template.
This suggests parameters are scoped to the template that defines them. A parameter defined only in an Environment Template would only be usable within that environment's scripts/variables, not in the Job Template's steps.
Possible clarification:
Job parameters are scoped to the template that defines them. A parameter defined in an Environment Template can only be referenced within that Environment Template. For a parameter to be accessible in both an Environment Template and a Job Template, it must be defined in both (with compatible types and constraints per the merging rules).
Section 1.2.1 discusses merging parameter definitions when the same parameter name appears in multiple templates. However, it doesn't address whether a parameter defined only in an Environment Template is accessible from the Job Template.
The current wording in §1.2 says:
This suggests parameters are scoped to the template that defines them. A parameter defined only in an Environment Template would only be usable within that environment's scripts/variables, not in the Job Template's steps.
Possible clarification: