ephraimbuddy commented on a change in pull request #274: URL: https://github.com/apache/airflow-site/pull/274#discussion_r464190491
########## File path: landing-pages/site/content/en/blog/implementing-stable-API-for-Apache-Airflow.md ########## @@ -0,0 +1,90 @@ +--- +title: "Implementing Stable API for Apache Airflow" +linkTitle: "Implementing Stable API for Apache Airflow" +author: "Ephraim Anierobi" +twitter: "ephraimbuddy" +github: "ephraimbuddy" +description: "An Outreachy intern's progress report on contributing to Apache Airflow REST API." +tags: ["REST API"] +date: "2020-07-19" +--- + +My [Outreachy internship](https://outreachy.org) is coming to its ends which is also the best time to look back and +reflect on the progress so far. + +The goal of my project is to Extend and Improve the Apache Airflow REST API. In this post, +I will be sharing my progress so far. + +We started a bit late implementing the REST API because it took time for the OpenAPI 3.0 +specification we were to use for the project to be merged. Thanks to [Kamil](https://github.com/mik-laj), +who paved the way for us to start implementing the REST API endpoints. Below are the endpoints I +implemented and the challenges I encountered, including how I overcame them. + +### Implementing The Read-Only Connection Endpoints +The [read-only connection endpoints](https://github.com/apache/airflow/pull/9095) were the first endpoint I implemented. Looking back, Review comment: It has two endpoints. ---------------------------------------------------------------- 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]
