Endpoint for dag_run status
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 34
- Forks
- 8
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 1
Description
Acceptance
- <DAG_ID>/dag_run endpoint on CKAN which gives a report with the status of the DAG
- Collect Airflow default API response for a DAG (for local and remote Airflow instances)
Note: This task won't provide any integration with GCP logs (see #69 ); it only collects the output of Airflow API
Tasks
- Create endpoint; DAG_RUN is optional. If no DAG_RUN is specified, list the most recent dag_runs
- If a DAG run is specified, retrieve info only for that particular RUN (note: when you trigger the DAG, the response brings the DAG_RUN (see #79)
- Return Airflow API response (local Airflow)
- Return Airflow API response (remote Airflow). It will require another integration with GCP
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the existing <DAG_ID>/dag_run endpoint and its Airflow API integration, including local and remote Airflow handling. Compare the current behavior with the checked acceptance items and review issues #69 and #79 for the stated boundaries. Done means the endpoint returns the relevant DAG-run status without adding GCP logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, python
- Domain
- api, backend, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100