GitHub user dave-csc added a comment to the discussion: How to share one env
with multiple projects in GUI?
Specifying a parent project will only inherit the project metadata (such as DB
connections, pipeline and workflow configurations, REST services, and so on).
But pipelines, workflows, and configuration files (even those you may have
setup to configure the parameters for the metadata above) won't be inherited.
What I personally do with my Hop workspace is setting up a `_root` project in
which all the metadata I need are set (plus some workflows and pipelines that
may be of "common use"). Then I set up the actual projects inheriting from
`_root`, and define their environments with the same configuration files: you
still need to declare them once in every environment you need, but at least
you're guaranteed that a change in one of the files (say, you have to change a
password) will reflect to all the projects and environments that are using it.
Regarding the "common use" pipelines and workflows: as mentioned, they are not
inherited but you can use them by specifying the full path in transform/actions
such as Pipeline/Workflow Executor or Simple mapping. Just be aware that
variables like `${PROJECT_HOME}` will refer to the _current_ project path, and
not the one in which resides the "common" pipeline, so you need to also adjust
the relations with eventual sub-pipelines and similar (tricky bit: you can
advantage of this `${PROJECT_HOME}` behaviour if you need a per-project
sub-pipeline in a common use super-pipeline 😅)
Hope this helps :)
GitHub link:
https://github.com/apache/hop/discussions/5470#discussioncomment-13637311
----
This is an automatically sent email for users@hop.apache.org.
To unsubscribe, please send an email to: users-unsubscr...@hop.apache.org
