Source Zoom: Fix authenticator bug and add missing fields

[ChristoGrab]

What

The Zoom connector has been down for some time, and due to lacking a sandbox account the updates to the authenticator introduced in 1.0.0 were never published. A test account has now been set up, and we are able to at least verify the ability to connect successfully to the API and sync data for multiple streams. All webinar streams remain untested at this time, and we do not currently plan to add integration tests for these streams as this is a Community connector.

How

Bugs

• Fixed auth_headers call in authenticator to return string rather than a dict
• Updated authenticator test to match actual implementation (grant_type is not set in config)

Schemas

• Added placeholder schemas for the transient meeting_list_tmp and webinar_list_tmp parent streams.
• Added missing fields to schemas and retyped meeting_id property in meeting_registration_questions stream

QA

• Updated test-config to current format
• Migrated to base image and moved dependency management to poetry
• Re-enabled the connector in registries

🚨🚨 User Impact

Users will be able to create connections and sync data again. This is a breaking change due to the new authenticator introduced in 1.0.0 and a retyped schema property. Users with existing connections will need to migrate by setting up their server-to-server apps in Zoom for the new authenticator, and refresh schemas if syncing data from the "meeting_registration_questions" stream.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	⬜️ Ignored (Inspect)	Visit Preview		Mar 12, 2024 7:15pm

[github-actions]

Before Merging a Connector Pull Request

Wow! What a great pull request you have here! 🎉

To merge this PR, ensure the following has been done/considered for each connector added or updated:

• PR name follows PR naming conventions
• Breaking changes are considered. If a Breaking Change is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan.
• Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
• You've updated the connector's metadata.yaml file any other relevant changes, including a breakingChanges entry for major version bumps. See metadata.yaml docs
• Secrets in the connector's spec are annotated with airbyte_secret
• All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...)
• Changelog updated in docs/integrations/<source or destination>/<name>.md with an entry for the new version. See changelog example
• Migration guide updated in docs/integrations/<source or destination>/<name>-migrations.md with an entry for the new version, if the version is a breaking change. See migration guide example
• If set, you've ensured the icon is present in the platform-internal repo. (Docs)

If the checklist is complete, but the CI check is failing,

1. Check for hidden checklists in your PR description

2. Toggle the github label checklist-action-run on/off to re-run the checklist CI.

[ChristoGrab]

The Zoom docs state that either a uuid or id can be provided. However, in my tests using the "uuid" in requests simply returned a "Meeting does not exist" message. By changing to "id" I was able to successfully fetch the records in our account.

[ChristoGrab]

Same as comment above

[bazarnov]

Looks good! But, the changes should be applied. LGTM once fixed.