dgesteves opened a new pull request, #9137: URL: https://github.com/apache/hop/pull/9137
Prompted by discussion #9123. A Workflow action in one project ran a workflow of another project, and with `hop-run -e Caller-dev -j External` the variables of the other project stayed empty. The docs already say an environment can have several configuration files, but not what that means when one project runs files of another, and the asker asked for it to be documented. This adds a short "Run a workflow from another project" section to the Projects and Environments page: - `hop-run -e` takes the project from the environment, so `-j` is ignored when `-e` is set (`ProjectsOptionPlugin.configure`). - A Workflow or Pipeline action runs the file in the project and environment of the calling workflow, with its variables and metadata. - To get the other project's variables, add its configuration file to the caller's environment, in Hop Gui or with hop-conf. `--environment-config-files` replaces the whole list (`ManageEnvironmentsOptionPlugin`), and the files are applied in order, the last one winning (`Project.modifyVariables`). For a single run, hop-run's `--environment-conf-files` adds the file without changing the environment. - Metadata (connections, run configurations) doesn't come with the configuration file. Setting the other project as the parent project brings it, along with the parent's project variables but not the configuration files of its environments. It also changes the `-j` row of the hop-run options from "Not needed when `-e` is set" to "Ignored when `-e` is set", with a link to the new section, and adds the section to the See also list of the Workflow action page. How I checked it: every statement against the code on main. The hop-conf fix itself I ran in the `apache/hop:2.19.0` Docker image with the projects from the discussion when I answered it. The three pages render with Asciidoctor without warnings, the new section's id matches both links, and the cross-manual reference and page description checks from `pr_build_docs.yml` pass. I did not run the Antora site build or `mvn clean install apache-rat:check` (no new files). Happy to change the wording or move the section if another page fits better. ------------------------ Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily: - [ ] 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. (not run, documentation-only change) - [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). Written with help from an agent (Claude Code); I reviewed it before opening. -- 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]
