Feat/databricks normalize brigad

.bumpversion.cfg

@@ -1,5 +1,5 @@
 [bumpversion]
-current_version = 0.44.3
+current_version = 0.50.18
 commit = False
 tag = False
 parse = (?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)(\-[a-z]+)?
@@ -12,14 +12,4 @@ serialize =
 
 [bumpversion:file:docs/operator-guides/upgrading-airbyte.md]
 
-[bumpversion:file:octavia-cli/Dockerfile]
-
-[bumpversion:file:octavia-cli/README.md]
-
 [bumpversion:file:run-ab-platform.sh]
-
-[bumpversion:file:octavia-cli/install.sh]
-
-[bumpversion:file:octavia-cli/setup.py]
-search = version="{current_version}"
-replace = version="{new_version}"

.github/CODEOWNERS

@@ -1,5 +1,5 @@
 # CDK and Connector Acceptance Tests
-/airbyte-cdk/ @airbytehq/connector-extensibility
+/airbyte-cdk/python @airbytehq/connector-extensibility
 /airbyte-integrations/connector-templates/ @airbytehq/connector-extensibility
 /airbyte-integrations/bases/connector-acceptance-tests/ @airbytehq/connector-operations
 
@@ -48,3 +48,4 @@
 /airbyte-integrations/connectors/destination-rockset/ @airbytehq/destinations
 /airbyte-integrations/connectors/destination-s3/ @airbytehq/destinations
 /airbyte-integrations/connectors/destination-snowflake/ @airbytehq/destinations
+/airbyte-integrations/connectors/destination-tidb/ @airbytehq/destinations

.github/ISSUE_TEMPLATE/1-issue-connector.yaml

@@ -0,0 +1,82 @@
+name: 🐛 Report a connector problem
+description: Use this template to report a problem using source or a destination connector
+labels: [type/bug, area/connectors, needs-triage]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        <p align="center">
+          <a target="_blank" href="https://airbyte.com">
+            <image>
+              <source srcset="https://raw.githubusercontent.com/airbytehq/airbyte/master/.github/octavia-issue-template.svg">
+              <img alt="octavia-welcome" src="https://raw.githubusercontent.com/airbytehq/airbyte/master/.github/octavia-issue-template.svg" width="auto" height="120">
+            </image>
+          </a>
+        </p>
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report...
+        Make sure you update this issue with a concise title and provide all information you have to help us debug the problem together.
+        Some examples of good titles following the convention:
+        <ul>
+          <li> Source Name: issue description </li>
+          <li> Destination Name: issue description </li>
+          <li> Source Postgres: Add `_ab_cdc_inserted_at` column for CDC syncs </li>
+          <li> Source Chargebee: cannot sync transaction objects</li>
+          <li> Source Snowflake: support for case sensitive parameters in connection string</li>
+          <li> Destination BigQuery: normalization incorrectly processes arrays</li>
+        </ul>
+        <br>
+        <p><small>Issues not following the template will be closed. </small></p>
+  - type: input
+    id: connector-name
+    attributes:
+      label: Connector Name
+      description: |
+        Insert only the name of the connector is having issue. 
+        Use the pattern source-postgres or destination-postgres. 
+        This will help us automatically label the issue to the correct teams.
+      placeholder: destination-mssql
+    validations:
+      required: true
+  - type: input
+    id: connector-version
+    attributes:
+      label: Connector Version
+      description: Give the connector version that has a problem. You can find it in the sync log file or the settings page.
+      placeholder: 0.2.63
+    validations:
+      required: true
+  - type: dropdown
+    id: step
+    attributes:
+      label: What step the error happened?
+      multiple: false
+      options:
+        - Configuring a new connector
+        - During the sync
+        - Updating the connector
+        - Other
+  - type: textarea
+    id: description
+    attributes:
+      label: Revelant information
+      description: Please give any additional information you have and steps to reproduce the problem.
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: |
+        Please copy and paste any relevant log output. 
+        This will be automatically formatted into code, so no need for backticks.
+        We strongly recommend to upload the log file for further debugging.
+      render: shell
+  - type: checkboxes
+    id: submit-pr
+    attributes:
+      label: Contribute
+      description: Are you willing to submit the fix?
+      options:
+        - label: Yes, I want to contribute
+          required: false

.github/ISSUE_TEMPLATE/2-issue-platform.yaml

@@ -0,0 +1,62 @@
+name: 🐛 Report a platform, infra or deployment bug
+description: Use this template when you have a problem operating Airbyte platform
+labels: [type/bug, area/platform, needs-triage]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        <p align="center">
+          <a target="_blank" href="https://airbyte.com">
+            <image>
+              <source srcset="https://raw.githubusercontent.com/airbytehq/airbyte/master/.github/octavia-issue-template.svg">
+              <img alt="octavia-welcome" src="https://raw.githubusercontent.com/airbytehq/airbyte/master/.github/octavia-issue-template.svg" width="auto" height="120">
+            </image>
+          </a>
+        </p>
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report...
+        Make sure to update this issue with a concise title and provide all information you have to 
+        help us debug the problem together. Issues not following the template will be closed.
+  - type: dropdown
+    id: deploy
+    validations:
+      required: true
+    attributes:
+      label: What method are you using to run Airbyte?
+      multiple: false
+      options:
+        - Docker
+        - Kubernetes
+  - type: input
+    id: platform-version
+    attributes:
+      label: Platform Version or Helm Chart Version
+      description: "Some examples are: (eg. 0.44.1, 0.30.0), you can find the version in the left bottom in Airbyte UI or in the .env / value.yaml file"
+    validations:
+      required: true
+  - type: dropdown
+    id: step
+    attributes:
+      label: What step the error happened?
+      multiple: false
+      options:
+        - On deploy
+        - During the Sync
+        - Upgrading the Platform or Helm Chart
+        - Other
+  - type: textarea
+    id: description
+    attributes:
+      label: Revelant information
+      description: Please give any additional information you have and steps to reproduce the problem.
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: |
+        Please copy and paste any relevant log output. 
+        This will be automatically formatted into code, so no need for backticks.
+        We strongly recommend to upload the log file for further debugging.
+      render: shell

.github/ISSUE_TEMPLATE/3-issue-cli.yaml

@@ -0,0 +1,42 @@
+name: 🐛 Report a problem while using the Octavia CLI
+description: Use this template when you discovered a CLI problem
+labels: [type/bug, area/octavia-cli, needs-triage]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        <p align="center">
+          <a target="_blank" href="https://airbyte.com">
+            <image>
+              <source srcset="https://raw.githubusercontent.com/airbytehq/airbyte/master/.github/octavia-issue-template.svg">
+              <img alt="octavia-welcome" src="htt ps://raw.githubusercontent.com/airbytehq/airbyte/master/.github/octavia-issue-template.svg" width="auto" height="120">
+            </image>
+          </a>
+        </p>
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report...
+        Make sure you update this issue with a concise title and provide all information you have to 
+        help us debug the problem together. Issues not following the template will be closed.
+  - type: input
+    id: cli-version
+    attributes:
+      label: Octavia CLI Version
+      description: Give the Octavia CLI version you're using.
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Revelant information
+      description: Please give any additional information you have and steps to reproduce the problem.
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: |
+        Please copy and paste any relevant log output. 
+        This will be automatically formatted into code, so no need for backticks.
+        We strongly recommend to upload the log file for further debugging.
+      render: shell

.github/ISSUE_TEMPLATE/5-feature-new-connector.yaml

@@ -0,0 +1,36 @@
+name: ✨ Request a new connector
+description: Request for new sources and destinations
+labels: [area/connectors, new-connector]
+body:
+  - type: input
+    id: connector-name
+    attributes:
+      label: Connector Name
+      description: What is the service or database you want to integrate
+    validations:
+      required: true
+  - type: dropdown
+    id: type
+    attributes:
+      label: What type of integration
+      multiple: false
+      options:
+        - Source
+        - Destination
+  - type: textarea
+    id: description
+    attributes:
+      label: Revelant Information
+      description: >-
+        Why do you need this integration? How does your team intend to use the data? This helps us understand the use case.
+        How often do you want to run syncs?
+        If this is an API source connector, which entities/endpoints do you need supported?
+        If the connector is for a paid service, can we name you as a mutual user when we subscribe for an account? Which company should we name?
+  - type: checkboxes
+    id: submit-pr
+    attributes:
+      label: Contribute
+      description: Are you willing to submit the fix?
+      options:
+        - label: Yes, I want to contribute
+          required: false

.github/ISSUE_TEMPLATE/6-feature-request.yaml

@@ -0,0 +1,20 @@
+name: ✨ Request a new feature
+description: Request to any new Airbyte features
+labels: [type/enhancement, needs-triage]
+body:
+  - type: dropdown
+    id: type
+    attributes:
+      label: What area the feature impact?
+      multiple: false
+      options:
+        - Connectors
+        - Airbyte Platform
+        - Helm Chart
+  - type: textarea
+    id: description
+    attributes:
+      label: Revelant Information
+      description: >-
+        What are you trying to do, and why is it hard? A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+        A clear and concise description of what you want to see happen, or the change you would like to see

.github/ISSUE_TEMPLATE/7-low-code-component.yaml

@@ -0,0 +1,38 @@
+name: ✨ Request a new low-code CDK component
+description: Use this to request new low-code CDK
+labels:
+  [
+    "team/extensibility",
+    "area/connector-builder",
+    "area/low-code/components",
+    "area/low-code",
+  ]
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: Component Description
+      description: Please describe the component you would like to see added to the Low-code CDK and why it's valuable
+    validations:
+      required: true
+  - type: textarea
+    id: proposed-schema
+    attributes:
+      label: Proposed YAML schema
+      description: If you can wave a magic wand, what would the YAML schema of the component you are suggesting look like?
+      value: |
+        ```yaml
+        ...
+        ```
+    validations:
+      required: true
+  - type: input
+    id: url
+    attributes:
+      label: Connector API Docs URL
+      description: To help us understand your request, please share a link to the API docs for the API you're trying to build, ideally pointing to the specific section of the docs relevant to your use case
+  - type: input
+    id: pr-url
+    attributes:
+      label: Pull Request URL
+      description: If there is a pull request which currently implements a custom component in lieu of having this component in the CDK, please link it

.github/ISSUE_TEMPLATE/8-documentation.yaml

@@ -0,0 +1,16 @@
+name: 📚 Request or report a problem with documenation
+description: For all docs typos, tutorials requests, etc.
+labels: [type/enhancement, area/documentation needs-triage]
+body:
+  - type: input
+    id: url
+    attributes:
+      label: Page URL
+      description: Paste the URL with problem when reporting an issue
+      placeholder: https://docs.airbyte.com/connector-development/connector-specification-reference
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: >-
+        It can be as pedantic as a typo or as titanic as an entire tutorial request.

.github/ISSUE_TEMPLATE/9-other.yaml

@@ -0,0 +1,16 @@
+name: 🤷 Others issues requests...
+description: Use this for whatever other issues you need to create an issue but don't have a specific category.
+labels: [needs-triage]
+body:
+  - type: input
+    id: topic
+    attributes:
+      label: Topic
+      description: Describe the topic with one or few words.
+    validations:
+      required: false
+  - type: textarea
+    id: description
+    attributes:
+      label: Revelant information
+      description: Please give any aditional information.