[
https://issues.apache.org/jira/browse/AIRFLOW-5548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16980914#comment-16980914
]
ASF GitHub Bot commented on AIRFLOW-5548:
-----------------------------------------
msb217 commented on pull request #6652: [AIRFLOW-5548] [AIRFLOW-5550] REST API
enhancement - dag info, task …
URL: https://github.com/apache/airflow/pull/6652
…listing, upstream/downstream tasks
Make sure you have checked _all_ steps below.
### Jira
- [ ] My PR addresses the following [Airflow
Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references
them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
- https://issues.apache.org/jira/browse/AIRFLOW-XXX
- In case you are fixing a typo in the documentation you can prepend your
commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
- In case you are proposing a fundamental code change, you need to create
an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)).
- In case you are adding a dependency, check if the license complies with
the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
### Description
- [X] Here are some details about my PR, including screenshots of any UI
changes:
I have added five new endpoints to the experimental REST API to allow for
clients to pull information about dags and the tasks that compose them. This is
useful for remote monitoring and execution. These endpoints include:
GET - DAG Info
GET - Dags in dagbag
GET - Tasks in a DAG
GET - Upstream Tasks
GET - Downstream Tasks
### Tests
- [ ] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
The REST API is experimental, howeverI will write unit tests if necessary
### Commits
- [X] My commits all reference Jira issues in their subject lines, and I
have squashed multiple commits if they address the same issue. In addition, my
commits follow the guidelines from "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
1. Subject is limited to 50 characters (not including Jira issue reference)
1. Subject does not end with a period
1. Subject uses the imperative mood ("add", not "adding")
1. Body wraps at 72 characters
1. Body explains "what" and "why", not "how"
### Documentation
- [X ] In case of new functionality, my PR adds documentation that describes
how to use it.
- All the public functions and the classes in the PR contain docstrings
that explain what it does
- If you implement backwards incompatible changes, please leave a note in
the [Updating.md](https://github.com/apache/airflow/blob/master/UPDATING.md) so
we can assign it to a appropriate release
All methods contains docstrings
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
> REST API: get DAGs
> ------------------
>
> Key: AIRFLOW-5548
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5548
> Project: Apache Airflow
> Issue Type: New Feature
> Components: api
> Affects Versions: 2.0.0
> Reporter: Norbert Biczo
> Assignee: Norbert Biczo
> Priority: Minor
>
> Like the already implemented [get
> pools|[https://airflow.apache.org/api.html#get--api-experimental-pools]] but
> with the DAGs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
