[PR] Ensure Airbyte Provider is Compatible with Cloud and Config APIs [airflow]

["chrishronek (via GitHub)" <gi...@apache.org>]

chrishronek opened a new pull request, #37943:
URL: https://github.com/apache/airflow/pull/37943

   <!--
    Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file
    distributed with this work for additional information
    regarding copyright ownership.  The ASF licenses this file
    to you under the Apache License, Version 2.0 (the
    "License"); you may not use this file except in compliance
    with the License.  You may obtain a copy of the License at
   
      http://www.apache.org/licenses/LICENSE-2.0
   
    Unless required by applicable law or agreed to in writing,
    software distributed under the License is distributed on an
    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
    KIND, either express or implied.  See the License for the
    specific language governing permissions and limitations
    under the License.
    -->
   
   <!-- Please keep an empty line above the dashes. -->
   ---
   closes: #35011
   
   This Change will allow Airbyte Cloud Users to utillize the Airbyte provider package in the same manner that the Airbyte OSS Users have. Unfortunately, Airbyte [currently supports two different APIs](https://docs.airbyte.com/api-documentation): 
   1. The [Config API](https://airbyte-public-api-docs.s3.us-east-2.amazonaws.com/rapidoc-api-docs.html) is for OSS Airbyte users self-hosting Airbyte. 
   2. The [Cloud API](https://reference.airbyte.com/reference/start) is for Airbyte Cloud users.
   
   Some noteable differences:
   - Authentication to the Config API is done via user:password basic auth while the Cloud API takes an API Token
   - Endpoint payloads are similar, but not identical
   - API Call methods are different (i.e., some `POST` requests in the config api are `GET` requests in the cloud API)
   
   To get around this, I'm suggesting we provide users the ability to specify `api_type="cloud_api"` on the operator/hook parameters. The default setting is `config_api` so that functionality doesn't break for existing users.
   
   **^ Add meaningful description above**
   Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information.
   In case of fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in a newsfragment file, named `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
   


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] Ensure Airbyte Provider is Compatible with Cloud and Config APIs [airflow]

["potiuk (via GitHub)" <gi...@apache.org>]

potiuk merged PR #37943:
URL: https://github.com/apache/airflow/pull/37943


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org