Status of testing Providers that were prepared on August 10, 2022 #25634
Labels
kind:meta
High-level information important to the community
testing status
Status of testing releases
Body
I have a kind request for all the contributors to the latest provider packages release.
Could you please help us to test the RC versions of the providers?
Let us know in the comment, whether the issue is addressed.
Those are providers that require testing as there were some substantial changes introduced:
Provider amazon: 5.0.0rc1
region_name
andconfig
in wrapper (#25336): @Taragolisextra[host]
in AWS's connection (#25494): @gmcrocettiProvider apache.drill: 2.2.0rc1
Provider apache.druid: 3.2.0rc1
Provider apache.hdfs: 3.1.0rc1
Provider apache.hive: 4.0.0rc1
Provider apache.livy: 3.1.0rc1
Provider apache.pinot: 3.2.0rc1
Provider common.sql: 1.1.0rc1
Provider cncf.kubernetes: 4.3.0rc1
Provider databricks: 3.2.0rc1
Provider dbt.cloud: 2.1.0rc1
Provider elasticsearch: 4.2.0rc1
Provider exasol: 4.0.0rc1
Provider google: 8.3.0rc1
Provider hashicorp: 3.1.0rc1
Provider jdbc: 3.2.0rc1
Provider microsoft.azure: 4.2.0rc1
test_connection
method to AzureContainerInstanceHook (#25362): @phanikumvProvider microsoft.mssql: 3.2.0rc1
Provider mysql: 3.2.0rc1
Provider neo4j: 3.1.0rc1
Provider odbc: 3.1.1rc1
Provider oracle: 3.3.0rc1
Provider postgres: 5.2.0rc1
Provider presto: 4.0.0rc1
PrestoToSlackOperator
(#25425): @eladkalProvider qubole: 3.2.0rc1
results_parser_callable
parameter in Qubole operator docs (#25514): @josh-fellProvider salesforce: 5.1.0rc1
Provider snowflake: 3.2.0rc1
Provider sqlite: 3.2.0rc1
Provider trino: 4.0.0rc1
Provider vertica: 3.2.0rc1
Provider yandex: 3.1.0rc1
The guidelines on how to test providers can be found in
Verify providers by contributors
Committer
The text was updated successfully, but these errors were encountered: