CFlyGoo opened a new issue, #10562: URL: https://github.com/apache/dolphinscheduler/issues/10562
### 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 I am trying to set some basic environment variables through **dolphinscheduler_env.sh**, and at the same time set some project-specific and volatile environment variables through the **Environment manage** feature. However, under the existing logic, this idea does not work. I can only make a copy of the basic environment variables in the **Environment manage** to take effect. I think it might be possible to improve this experience by setting and overriding multiple levels of environment variables ### Use case E.g In a Python task, I can `export PYTHONPATH=xxx` in **dolphinscheduler_env.sh** to make all projects reference some base packages without having to go through **Environment manage** or **Resources** authorization to set them one by one. In the project-specific **Environment manage** or **Resources** authorization, only the specific part of the project is concerned. Such as `export PYTHONPATH=yyy:$PYTHONPATH`. ### Related issues _No response_ ### Are you willing to submit a PR? - [X] 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]
