* enable py spec compatibility tests * add missing properties * use expected spec file instead of the source spec.json + use dummy config file * add missing files for the clickhouse * move test files to the integration-test from the unit test folder * add missing files to cockroachdb * add missing files to db2 + fix spec format * add missing files to elasticsearch + fix spec format * add missing files to jdbc * add missing files to mongodb_v2 + fix spec format * add missing files to mssql + fix spec format * add missing files to mysql + fix spec format * add missing files to postgres + fix spec format * add missing files to oracle + fix spec format * add missing files to redshift * add missing files to sftp * add missing files to snowflake + fix spec format * add missing files to tidb * add missing files to kafka - fix spec format * airbyte-source-acceptance-test added Signed-off-by: Sergey Chvalyuk <grubberr@gmail.com> * add missing import * Delete acceptance-test-config.yml * Delete acceptance-test-docker.sh * Update build.gradle * Update build.gradle * format * revert changes * manual .sh files format * upd expected spec * format * fix SAT after master merge Signed-off-by: Sergey Chvalyuk <grubberr@gmail.com> Co-authored-by: Sergey Chvalyuk <grubberr@gmail.com>
BigQuery Test Configuration
In order to test the BigQuery source, you need a service account key file.
Community Contributor
As a community contributor, you will need access to a GCP project and BigQuery to run tests.
- Go to the
Service Accountspage on the GCP console - Click on `+ Create Service Account" button
- Fill out a descriptive name/id/description
- Click the edit icon next to the service account you created on the
IAMpage - Add the
BigQuery Data EditorandBigQuery Userrole - Go back to the
Service Accountspage and use the actions modal toCreate Key - Download this key as a JSON file
- Move and rename this file to
secrets/credentials.json
Airbyte Employee
- Access the
BigQuery Integration Test Usersecret on Rippling under theEngineeringfolder - Create a file with the contents at
secrets/credentials.json