hokie-chan opened a new issue, #14241:
URL: https://github.com/apache/dolphinscheduler/issues/14241

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar feature requirement.
   
   
   ### Description
   
   Inspired by https://github.com/apache/dolphinscheduler/issues/14076, we can 
do one more step, add tenant-level parameters, so that to achive a real 
"global" parameter feature (the current "global parameters" is just for process 
definition, not literally "global")
   
   Currently, DS has local and global parameters. Note that Global parameters 
only take effect inside the workflow
   Add project-level parameters so that all workflows under the same project 
can use these project-level parameters.
   
   ### Why we need project-level parameters
   Usually, we have UAT and PROD environments, the paths, URLs, IPs and such 
kind of things always different. if we tested processes/tasks in UAT, we may 
want to export the definitions and then deploy to PROD, then the differnt 
paths/URLs/IPs can be a big trouble.
   Once tenant level parameters are available, we can use tenant-level 
parameters to replace the "hard-code" paths/URLs/IPs in processes/tasks, then 
we can simply export definitions from UAT and directly import to PROD.
   
   ### Use case
   
   tenant level parameters are available, in backend and also in UI
   
   ### Related issues
   
   https://github.com/apache/dolphinscheduler/issues/14076
   https://github.com/apache/dolphinscheduler/issues/14214
   https://github.com/apache/dolphinscheduler/issues/14218
   
   ### Are you willing to submit a PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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]

Reply via email to