You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assuming a split up of the orb executors, jobs and commands, it is more idiomatic to generate a crosscutting scope for parameters and the respective arguments. Parameters could be derived implicitly from their usage and imported from a crosscutting scope where all parameters for executors, commands and jobs are defined.
A parameter is to be imported if it is passed over as argument or if it is used in the steps or executor section. To generify, parameters are always and only then to be imported if they are mentioned as << parameters.var >> at any place in the orb file before the import. Parameters that are not supposed to be imported in a crosscutting way, can still be specified and referenced directly in the file without the parameters. prefix.
The text was updated successfully, but these errors were encountered:
Assuming a split up of the orb executors, jobs and commands, it is more idiomatic to generate a crosscutting scope for parameters and the respective arguments. Parameters could be derived implicitly from their usage and imported from a crosscutting scope where all parameters for executors, commands and jobs are defined.
A parameter is to be imported if it is passed over as argument or if it is used in the steps or executor section. To generify, parameters are always and only then to be imported if they are mentioned as
<< parameters.var >>
at any place in the orb file before the import. Parameters that are not supposed to be imported in a crosscutting way, can still be specified and referenced directly in the file without theparameters.
prefix.The text was updated successfully, but these errors were encountered: