Adalennis opened a new pull request, #9002:
URL: https://github.com/apache/hop/pull/9002

   Fixes #2517
   
   Passing parameters to a child is documented since #8101 (Passing parameters 
to a child pipeline or workflow). This adds the rest of the issue: how to 
declare a parameter and give it a value.
   
   - New page Variables › Working with parameters: declare a parameter, use it, 
and give it a value from Hop Gui (the Run Options dialog), from hop-run (-p) or 
from another pipeline or workflow (linking to the parameter-passing rules).
   - Links to it from the properties, run, hop-run, variables, 
fields-parameters-variables and parameter-passing pages.
   - variables.adoc: a project variable wins over an environment variable of 
the same name (Project.modifyVariables applies the project variables last).
   
   
   - [x] Run `mvn clean install apache-rat:check` to make sure basic checks 
pass. A more thorough check will be performed on your pull request 
automatically.
   - [x] If you have a group of commits related to the same change, please 
squash your commits into one and force push your branch using `git rebase -i`.
   - [x] Mention the appropriate issue in your description (for example: 
`addresses #123`), if applicable.
   
   To make clear that you license your contribution under the [Apache License 
Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
   - [x] I hereby declare this contribution to be licensed under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   - [ ] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to