dill21yu commented on issue #17501:
URL:
https://github.com/apache/dolphinscheduler/issues/17501#issuecomment-3290883884
> Basically LGTM, I would prefer to move this into datasource.
@ruanwenjun Thanks for the feedback!
I agree with your suggestion to leverage the existing Datasource module to
manage configurations for third-party systems. This aligns well with how
DolphinScheduler already handles non-JDBC resources like SSH โ treating a
REST-managed external system (e.g., SeaTunnel, custom platforms ) as a
"logical endpoint" with connection metadata.
Hereโs an updated proposal based on your input:
๐ง **Use Datasource for Third-party System Configuration**
- Introduce a new datasource type: `Generic API Connector` (or `REST API
Endpoint`) in the Datasource module.
- Store configuration including:
- Base URL
- Authentication method
- API endpoint templates (for list, start, status check, stop)
๐ **Task Integration**
- A new **"Generic API Task"** will reference a configured `Generic API
Connector`.
- When selected, the UI will:
1. Fetch available jobs from the `/list` endpoint (via backend proxy).
2. Allow users to select one job.
3. Use the mapped APIs to start, poll status, and stop the job.
This approach keeps configuration centralized and secure, while enabling
flexible integration without requiring custom plugins for each system.
Could you or other maintainers please advise if there are any other modules
(e.g., security, alerting, resource management) that may also need to be
considered or modified to fully support this feature? I'd appreciate any
additional suggestions to ensure the design is aligned with DolphinScheduler's
architecture.
--
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]
