1dabc6208e
* Add optional tags field * Remove duplicate icons * Add programming tags to all * Update docs * supportUrl -> documentationUrl * Ensure one language tag is applied * Add keyvalue check * rebase and fix tests * Format * Add cache buster * Improve test * Automated Commit - Formatting Changes * Update error * Fix missing tags * Fix scaffold --------- Co-authored-by: Octavia Squidington III <octavia-squidington-iii@sers.noreply.github.com> Co-authored-by: bnchrch <bnchrch@users.noreply.github.com>
Google PubSub Test Configuration
In order to test the PubSub destination, you need a service account key file.
Community Contributor
As a community contributor, you will need access to a GCP project and PubSub 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
Pub/Sub Editorrole - 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
google pubsub test credentials.jsonsecret on Lastpass under theshared-integration-testfolder - Create a file with the contents at
secrets/credentials.json