CarlosJuncher03 commented on issue #7908: URL: https://github.com/apache/hop/issues/7908#issuecomment-5282137951
That makes sense. I agree that hard-blocking the execution could become inconvenient during development and would probably lead people to disable the restriction. After looking at the data quality / quality gate approach, I think perhaps the original proposal could be simplified. Instead of preventing direct execution, a pipeline could optionally declare metadata indicating that it normally depends on another workflow or pipeline as its expected entry point or preparation step. Then, when someone executes that pipeline directly from Hop GUI, Hop could display a warning such as: "This pipeline normally depends on workflow X being executed first." The user could then either continue with the direct execution or choose an action like "Run through workflow X". This would make the dependency visible without introducing dependency-state management, execution time windows, or hard enforcement. In production, the orchestrator would still be responsible for executing everything in the correct order. The metadata would mainly help developers and operators understand that a pipeline is normally not intended to be executed independently. This would also preserve the ability to execute the pipeline directly when needed for development, debugging, or manual corrections. So perhaps this is less about enforcing a required entry point and more about declaring an expected entry point/dependency and warning when it is bypassed. -- 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]
