dsanderbi commented on issue #2596: URL: https://github.com/apache/hop/issues/2596#issuecomment-3566640454
Hi @hansva, i have a question regarding the feature request. **What behavior exactly did you have in mind?** If we introduce the variables ```bash ENV HOP_PARENT_PROJECT_NAME= ENV HOP_PARENT_PROJECT_CONFIG_FILE_NAME=parent-project-config.json ENV HOP_PARENT_PROJECT_FOLDER= ``` in the Dockerfile, we could add a check in `load-and-execute.sh` right after the `HOP_PROJECT_FOLDER` (since it doesn't make sense to add a parent without the main project). --- The downside is that only one hierarchy level can be passed. --- Compared to the GUI if you have for example three projects like `project-super`, `project-main` and `project-parent` where - `project-parent` is the parent of `project-main` - `project-main` is the parent of `project-super` the `project-super` also can access metadata from `project-parent` This would not be possible with implementation using additional Docker variables. Other approaches, like creating a project for each folder mounted under `/files`, are difficult because we don’t know which of the contained projects belongs to which parent. --- **Would it be sufficient for you if only one level of inheritance could be specified for the Container?** --- I tested this with a short-lived container, and there the metadata passing works (e.g., a database connection defined in the parent and then used in the main project). When testing with a long-lived container, for example with a service defined in the parent, services coming from the parent cannot be accessed, unless you adjust the path in the main project but then it also gets changed in the parent. The same behavior occurs in the GUI. <img width="449" height="50" alt="Image" src="https://github.com/user-attachments/assets/2391f0e9-597d-40d4-b2fa-cf4ffb104a5c"; /> For this to work, there would need to be a `PARENT_PROJECT_HOME`as requested here #2331 which also supports the idea that this could be solved using the additional variables. -- 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]
