S3, Google Drive, Azure Blob Storage: Update cdk

[flash1293]

This PR rolls out #33300 and #32781 to all relevant source connectors.

As remote processing is currently experiencing the issue described in https://github.com/airbytehq/airbyte-internal-issues/issues/6199, this option is temporarily hidden from the spec. Once the platform supports managing secrets in arrays correctly, this limitation will be lifted.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 15, 2023 11:22am

[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.

[flash1293]

@clnoll @aaronsteers pinging you on this - as we can't roll out the remote processing feature right now without weird behavior, I hid it temporarily by adjusting the spec in the connector. Once the linked issue is resolved, it can be shown "properly"

[clnoll]

The change looks good to me @flash1293, just one small question.

[clnoll]

Will this have to be reverted when the platform issue is fixed? Couldn't quite see why google drive had this method but the other sources don't.

[flash1293]

This has been moved into the abstract file based spec and doesn't have to be moved back. It's only on google drive because the other connectors didn't have oneOfs in their spec which made it necessary (Google drive has two auth modes)