You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by "hokie-chan (via GitHub)" <gi...@apache.org> on 2023/05/31 02:44:34 UTC

[GitHub] [dolphinscheduler] hokie-chan opened a new issue, #14241: [Feature][Parameters] Support of tenant-level parameters

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: commits-unsubscribe@dolphinscheduler.apache.org.apache.org

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


[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #14241: [Feature][Parameters] Support of tenant-level parameters

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #14241:
URL: https://github.com/apache/dolphinscheduler/issues/14241#issuecomment-1569416691

   Thank you for your feedback, we have received your issue, Please wait patiently for a reply.
   * In order for us to understand your request as soon as possible, please provide detailed information, version or pictures.
   * If you haven't received a reply for a long time, you can [join our slack](https://s.apache.org/dolphinscheduler-slack) and send your question to channel `#troubleshooting`


-- 
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: commits-unsubscribe@dolphinscheduler.apache.org

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