Prepare Google Sheets, Google Drive, Apify dataset and connector templates for airbyte-lib

[flash1293]

This PR prepares some exemplary python connectors for airbyte-lib consumption.

The main changes are:

• Move the entrypoint logic into a run.py file within the package that will be published
• Call this logic from the top level main.py file
• Make the connector available as a console script under the name of the source by using the newly introduced entrypoint logic

To make new connectors compatible with airbyte-lib from the start, the connector templates are updated as well.

[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		Dec 18, 2023 5:18pm

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

[girarda]

why is the template file different from the connector's implementation?

I'd expect this file to only contain the run method and for the if __name__ == "__main__" to be in the main.py file

[flash1293]

Good catch @girarda ! This is exactly how it should look like, fixed!

[girarda]

!

[aaronsteers]

In the long run, I'd like to further reduce the amount of code needed, but this is already very well tuned. Also in the long run, it would be good to make airbyte-ci depend on the CLI entrypoint or the new run:run pattern, instead of ../main.py which is outside the module folder.