emptyOVO opened a new issue, #11504: URL: https://github.com/apache/inlong/issues/11504
### Description According pr: #11484 and pr: #11486 1. At present, manager and dashboard only support the selection of third-party engines, but they cannot be configured directly, requiring manual modification of the properties file and then recompilation, which makes it inefficient and not easy to use from the user's perspective. If we need to change the relevant configuration in the configuration file every time, we will not be able to handle multiple tasks that require multiple engines to schedule  we can see there is no place for configure engine details personally think related configuration can be configured in dashboard and call in service may be a good idea 2. The present configuration of DolphinScheduler is incorrect, DS engine also be able to select schedule interval and unit, which can be handle in `DolphinScheduleUtils` in pr: #11468  3. Some configuration may needs to be config in dashboard * for Airflow: according pr: #11479 ,there may need configs below ```properties # Airflow API URL airflow.baseUrl= airflow.connection.id= airflow.username= airflow.password= # Please confirm if it is a loopback address inlong.manager.host= # DAG Deleter and Creator ID airflow.cleaner.id= airflow.creator.id= ``` * for DolphinScheduler: according pr: #11468 ,there may need configs below ```properties # DolphinScheduler related config inlong.schedule.dolphinscheduler.url= inlong.schedule.dolphinscheduler.token= ``` ### Use case _No response_ ### Are you willing to submit 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]
