Skip to content

Conversation

@eladkal
Copy link
Contributor

@eladkal eladkal commented Mar 9, 2025

Summary of prepared documentation:

Success: 89

airbyte alibaba amazon apache.beam apache.cassandra apache.drill apache.druid apache.flink apache.hdfs apache.hive apache.iceberg apache.impala apache.kylin apache.livy apache.pig apache.pinot
apache.spark apprise arangodb asana atlassian.jira celery cloudant cncf.kubernetes cohere common.compat common.io common.sql databricks datadog dbt.cloud dingding discord docker elasticsearch exasol
facebook ftp github grpc hashicorp http imap influxdb jdbc jenkins microsoft.azure microsoft.mssql microsoft.psrp microsoft.winrm mongo mysql neo4j odbc openai openfaas openlineage opensearch opsgenie
oracle pagerduty papermill pgvector pinecone postgres presto qdrant redis salesforce samba segment sendgrid sftp singularity slack smtp snowflake sqlite ssh standard tableau telegram teradata trino
vertica weaviate yandex ydb zendesk

Docs only: 1

google

Skipped by user: 3

apache.kafka common.messaging fab

Skipped info:

kafka and google are skipped until we have clarifications on #47056 (comment)

common.messaging is draft - I think we need to mark this as not ready?

Copy link
Member

@potiuk potiuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Big one :) .. Just a few small doc issues left :)

@potiuk
Copy link
Member

potiuk commented Mar 9, 2025

common.messaging is draft - I think we need to mark this as not ready?

We could also make it 0.1, I do not think that there is harm in releasing it early.

@potiuk
Copy link
Member

potiuk commented Mar 9, 2025

We could also make it 0.1, I do not think that there is harm in releasing it early.

I reserved it in PyPI BTW.

@eladkal
Copy link
Contributor Author

eladkal commented Mar 9, 2025

We could also make it 0.1, I do not think that there is harm in releasing it early.

We could but then we also didn't do it for edge provider?

@potiuk
Copy link
Member

potiuk commented Mar 9, 2025

We could but then we also didn't do it for edge provider?

We could.

@eladkal eladkal merged commit 492ecfe into apache:main Mar 9, 2025
70 checks passed
@eladkal eladkal deleted the providers branch March 9, 2025 13:49
azharizz pushed a commit to azharizz/airflow that referenced this pull request Mar 9, 2025
* Prepare docs for Mar 1st wave of providers
nailo2c pushed a commit to nailo2c/airflow that referenced this pull request Apr 4, 2025
* Prepare docs for Mar 1st wave of providers
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants