[GitHub] [hop] hansva opened a new issue, #2331: [Feature Request]: Add variable PARENT_PROJECT_HOME

["hansva (via GitHub)" <gi...@apache.org>]

hansva opened a new issue, #2331:
URL: https://github.com/apache/hop/issues/2331

   ### What would you like to happen?
   
   Migration: https://issues.apache.org/jira/browse/HOP-4468
   
   Currently while the structure of a HOP project is configurable with a cascading set of project definitions (theoretically going on infinitely) there is no "easy" way to access the parent project directory ala PROJECT_HOME. I don't believe it's necessary to have more than the PARENT_PROJECT_HOME and ROOT_PROJECT_HOME (possibly GRANDPARENT_PROJECT_HOME).
   
   The use case here is avoid using ${PROJECT_HOME}/../SHARED_PIPELINES/example.hpl when configuring an action/transform step and instead using ${PARENT_PROJECT_HOME}/SHARED_PIPELINES/example.hpl.
   
   This offers the flexibility of moving directories without breaking code. Basically it offers easy access to sister project code.
   
   Additional note: I'd also like to use this to point to Environment JSON files that have confidential information that is located in a project outside the GIT repository of the current project. In many of my own cases I am building multiple micro/mini projects around a master project and it's much simpler to include all the "secrets" in a different private git project repo basically filled with JSON files. So I am having to include ${PROJECT_HOME}/../secrets/project-secrets-dev.json in each environment definition.
   
   ### Issue Priority
   
   Priority: 3
   
   ### Issue Component
   
   Component: Metadata


-- 
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: issues-unsubscribe@hop.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org