airbyte-source-google-sheets 0.3.14__tar.gz → 0.3.15.dev202402081036__tar.gz

airbyte_source_google_sheets-0.3.15.dev202402081036/PKG-INFO

@@ -0,0 +1,118 @@
+Metadata-Version: 2.1
+Name: airbyte-source-google-sheets
+Version: 0.3.15.dev202402081036
+Summary: Source implementation for Google Sheets.
+Home-page: https://airbyte.com
+License: MIT
+Author: Airbyte
+Author-email: contact@airbyte.io
+Requires-Python: >=3.9,<4.0
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Requires-Dist: PyYAML (==6.0.1)
+Requires-Dist: Unidecode (==1.3.8)
+Requires-Dist: airbyte-cdk (==0.51.8)
+Requires-Dist: backoff (==2.2.1)
+Requires-Dist: google-api-python-client (==2.114.0)
+Requires-Dist: google-auth-httplib2 (==0.2.0)
+Requires-Dist: pydantic (==1.9.2)
+Requires-Dist: requests (==2.31.0)
+Project-URL: Documentation, https://docs.airbyte.com/integrations/sources/google-sheets
+Project-URL: Repository, https://github.com/airbytehq/airbyte
+Description-Content-Type: text/markdown
+
+# Google-Sheets source connector
+
+
+This is the repository for the Google-Sheets source connector, written in Python.
+For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/google-sheets).
+
+## Local development
+
+### Prerequisites
+* Python (~=3.9)
+* Poetry (~=1.7) - installation instructions [here](https://python-poetry.org/docs/#installation)
+
+
+### Installing the connector
+From this connector directory, run:
+```bash
+poetry install --with dev
+```
+
+
+### Create credentials
+**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.com/integrations/sources/google-sheets)
+to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_google_sheets/spec.yaml` file.
+Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
+See `sample_files/sample_config.json` for a sample config file.
+
+
+### Locally running the connector
+```
+poetry run source-google-sheets spec
+poetry run source-google-sheets check --config secrets/config.json
+poetry run source-google-sheets discover --config secrets/config.json
+poetry run source-google-sheets read --config secrets/config.json --catalog sample_files/configured_catalog.json
+```
+
+### Running unit tests
+To run unit tests locally, from the connector directory run:
+```
+poetry run pytest unit_tests
+```
+
+### Building the docker image
+1. Install [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md)
+2. Run the following command to build the docker image:
+```bash
+airbyte-ci connectors --name=source-google-sheets build
+```
+
+An image will be available on your host with the tag `airbyte/source-google-sheets:dev`.
+
+
+### Running as a docker container
+Then run any of the connector commands as follows:
+```
+docker run --rm airbyte/source-google-sheets:dev spec
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-google-sheets:dev check --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-google-sheets:dev discover --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-google-sheets:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
+```
+
+### Running our CI test suite
+You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
+```bash
+airbyte-ci connectors --name=source-google-sheets test
+```
+
+### Customizing acceptance Tests
+Customize `acceptance-test-config.yml` file to configure acceptance tests. See [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference) for more information.
+If your connector requires to create or destroy resources for use during acceptance tests create fixtures for it and place them inside integration_tests/acceptance.py.
+
+### Dependency Management
+All of your dependencies should be managed via Poetry. 
+To add a new dependency, run:
+```bash
+poetry add <package-name>
+```
+
+Please commit the changes to `pyproject.toml` and `poetry.lock` files.
+
+## Publishing a new version of the connector
+You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
+1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-google-sheets test`
+2. Bump the connector version (please follow [semantic versioning for connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#semantic-versioning-for-connectors)): 
+    - bump the `dockerImageTag` value in in `metadata.yaml`
+    - bump the `version` value in `pyproject.toml`
+3. Make sure the `metadata.yaml` content is up to date.
+4. Make sure the connector documentation and its changelog is up to date (`docs/integrations/sources/google-sheets.md`).
+5. Create a Pull Request: use [our PR naming conventions](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#pull-request-title-convention).
+6. Pat yourself on the back for being an awesome contributor.
+7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
+8. Once your PR is merged, the new version of the connector will be automatically published to Docker Hub and our connector registry.

airbyte_source_google_sheets-0.3.15.dev202402081036/README.md

@@ -0,0 +1,91 @@
+# Google-Sheets source connector
+
+
+This is the repository for the Google-Sheets source connector, written in Python.
+For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/google-sheets).
+
+## Local development
+
+### Prerequisites
+* Python (~=3.9)
+* Poetry (~=1.7) - installation instructions [here](https://python-poetry.org/docs/#installation)
+
+
+### Installing the connector
+From this connector directory, run:
+```bash
+poetry install --with dev
+```
+
+
+### Create credentials
+**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.com/integrations/sources/google-sheets)
+to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_google_sheets/spec.yaml` file.
+Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
+See `sample_files/sample_config.json` for a sample config file.
+
+
+### Locally running the connector
+```
+poetry run source-google-sheets spec
+poetry run source-google-sheets check --config secrets/config.json
+poetry run source-google-sheets discover --config secrets/config.json
+poetry run source-google-sheets read --config secrets/config.json --catalog sample_files/configured_catalog.json
+```
+
+### Running unit tests
+To run unit tests locally, from the connector directory run:
+```
+poetry run pytest unit_tests
+```
+
+### Building the docker image
+1. Install [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md)
+2. Run the following command to build the docker image:
+```bash
+airbyte-ci connectors --name=source-google-sheets build
+```
+
+An image will be available on your host with the tag `airbyte/source-google-sheets:dev`.
+
+
+### Running as a docker container
+Then run any of the connector commands as follows:
+```
+docker run --rm airbyte/source-google-sheets:dev spec
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-google-sheets:dev check --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-google-sheets:dev discover --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-google-sheets:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
+```
+
+### Running our CI test suite
+You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
+```bash
+airbyte-ci connectors --name=source-google-sheets test
+```
+
+### Customizing acceptance Tests
+Customize `acceptance-test-config.yml` file to configure acceptance tests. See [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference) for more information.
+If your connector requires to create or destroy resources for use during acceptance tests create fixtures for it and place them inside integration_tests/acceptance.py.
+
+### Dependency Management
+All of your dependencies should be managed via Poetry. 
+To add a new dependency, run:
+```bash
+poetry add <package-name>
+```
+
+Please commit the changes to `pyproject.toml` and `poetry.lock` files.
+
+## Publishing a new version of the connector
+You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
+1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-google-sheets test`
+2. Bump the connector version (please follow [semantic versioning for connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#semantic-versioning-for-connectors)): 
+    - bump the `dockerImageTag` value in in `metadata.yaml`
+    - bump the `version` value in `pyproject.toml`
+3. Make sure the `metadata.yaml` content is up to date.
+4. Make sure the connector documentation and its changelog is up to date (`docs/integrations/sources/google-sheets.md`).
+5. Create a Pull Request: use [our PR naming conventions](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#pull-request-title-convention).
+6. Pat yourself on the back for being an awesome contributor.
+7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
+8. Once your PR is merged, the new version of the connector will be automatically published to Docker Hub and our connector registry.

airbyte_source_google_sheets-0.3.15.dev202402081036/pyproject.toml

@@ -0,0 +1,40 @@
+[build-system]
+requires = [
+    "poetry-core>=1.0.0",
+]
+build-backend = "poetry.core.masonry.api"
+
+[tool.poetry]
+version = "0.3.15.dev202402081036"
+name = "airbyte-source-google-sheets"
+description = "Source implementation for Google Sheets."
+authors = [
+    "Airbyte <contact@airbyte.io>",
+]
+license = "MIT"
+readme = "README.md"
+documentation = "https://docs.airbyte.com/integrations/sources/google-sheets"
+homepage = "https://airbyte.com"
+repository = "https://github.com/airbytehq/airbyte"
+packages = [
+    { include = "source_google_sheets" },
+]
+
+[tool.poetry.dependencies]
+python = "^3.9"
+requests = "==2.31.0"
+backoff = "==2.2.1"
+google-auth-httplib2 = "==0.2.0"
+Unidecode = "==1.3.8"
+pydantic = "==1.9.2"
+airbyte-cdk = "==0.51.8"
+google-api-python-client = "==2.114.0"
+PyYAML = "==6.0.1"
+
+[tool.poetry.scripts]
+source-google-sheets = "source_google_sheets.run:run"
+
+[tool.poetry.group.dev.dependencies]
+requests-mock = "^1.9.3"
+pytest-mock = "^3.6.1"
+pytest = "^6.1"

airbyte-source-google-sheets-0.3.14/PKG-INFO

@@ -1,77 +0,0 @@
-Metadata-Version: 2.1
-Name: airbyte-source-google-sheets
-Version: 0.3.14
-Summary: Source implementation for Google Sheets.
-Author: Airbyte
-Author-email: contact@airbyte.io
-Description-Content-Type: text/markdown
-Requires-Dist: airbyte-cdk
-Requires-Dist: backoff
-Requires-Dist: requests
-Requires-Dist: google-auth-httplib2
-Requires-Dist: google-api-python-client
-Requires-Dist: PyYAML~=6.0
-Requires-Dist: pydantic~=1.9.2
-Requires-Dist: Unidecode
-Provides-Extra: tests
-Requires-Dist: requests-mock~=1.9.3; extra == "tests"
-Requires-Dist: pytest-mock~=3.6.1; extra == "tests"
-Requires-Dist: pytest~=6.1; extra == "tests"
-
-# Pypi Source
-
-This is the repository for the Pypi configuration based source connector.
-For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/pypi).
-
-
-**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/pypi)
-to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_pypi/spec.yaml` file.
-Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
-See `integration_tests/sample_config.json` for a sample config file.
-
-**If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source pypi test creds`
-and place them into `secrets/config.json`.
-
-
-
-**Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**
-```bash
-airbyte-ci connectors --name source-pypi build
-```
-
-An image will be built with the tag `airbyte/source-pypi:dev`.
-
-**Via `docker build`:**
-```bash
-docker build -t airbyte/source-pypi:dev .
-```
-
-Then run any of the connector commands as follows:
-```
-docker run --rm airbyte/source-pypi:dev spec
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-pypi:dev check --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-pypi:dev discover --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-pypi:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
-```
-
-You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
-```bash
-airbyte-ci connectors --name=source-google-sheets test
-```
-
-Customize `acceptance-test-config.yml` file to configure tests. See [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference) for more information.
-If your connector requires to create or destroy resources for use during acceptance tests create fixtures for it and place them inside integration_tests/acceptance.py.
-
-All of your dependencies should go in `setup.py`, NOT `requirements.txt`. The requirements file is only used to connect internal Airbyte dependencies in the monorepo for local development.
-We split dependencies between two groups, dependencies that are:
-* required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
-* required for the testing need to go to `TEST_REQUIREMENTS` list
-
-You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
-1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-google-sheets test`
-2. Bump the connector version in `metadata.yaml`: increment the `dockerImageTag` value. Please follow [semantic versioning for connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#semantic-versioning-for-connectors).
-3. Make sure the `metadata.yaml` content is up to date.
-4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/google-sheets.md`).
-5. Create a Pull Request: use [our PR naming conventions](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#pull-request-title-convention).
-6. Pat yourself on the back for being an awesome contributor.
-7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.

airbyte-source-google-sheets-0.3.14/README.md

@@ -1,67 +0,0 @@
-# Pypi Source
-
-This is the repository for the Pypi configuration based source connector.
-For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/pypi).
-
-## Local development
-
-#### Create credentials
-**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/pypi)
-to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_pypi/spec.yaml` file.
-Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
-See `integration_tests/sample_config.json` for a sample config file.
-
-**If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source pypi test creds`
-and place them into `secrets/config.json`.
-
-### Locally running the connector docker image
-
-
-#### Build
-**Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**
-```bash
-airbyte-ci connectors --name source-pypi build
-```
-
-An image will be built with the tag `airbyte/source-pypi:dev`.
-
-**Via `docker build`:**
-```bash
-docker build -t airbyte/source-pypi:dev .
-```
-
-#### Run
-Then run any of the connector commands as follows:
-```
-docker run --rm airbyte/source-pypi:dev spec
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-pypi:dev check --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-pypi:dev discover --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-pypi:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
-```
-
-## Testing
-You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
-```bash
-airbyte-ci connectors --name=source-google-sheets test
-```
-
-### Customizing acceptance Tests
-Customize `acceptance-test-config.yml` file to configure tests. See [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference) for more information.
-If your connector requires to create or destroy resources for use during acceptance tests create fixtures for it and place them inside integration_tests/acceptance.py.
-
-## Dependency Management
-All of your dependencies should go in `setup.py`, NOT `requirements.txt`. The requirements file is only used to connect internal Airbyte dependencies in the monorepo for local development.
-We split dependencies between two groups, dependencies that are:
-* required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
-* required for the testing need to go to `TEST_REQUIREMENTS` list
-
-### Publishing a new version of the connector
-You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
-1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-google-sheets test`
-2. Bump the connector version in `metadata.yaml`: increment the `dockerImageTag` value. Please follow [semantic versioning for connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#semantic-versioning-for-connectors).
-3. Make sure the `metadata.yaml` content is up to date.
-4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/google-sheets.md`).
-5. Create a Pull Request: use [our PR naming conventions](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#pull-request-title-convention).
-6. Pat yourself on the back for being an awesome contributor.
-7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
-

airbyte-source-google-sheets-0.3.14/airbyte_source_google_sheets.egg-info/PKG-INFO

@@ -1,77 +0,0 @@
-Metadata-Version: 2.1
-Name: airbyte-source-google-sheets
-Version: 0.3.14
-Summary: Source implementation for Google Sheets.
-Author: Airbyte
-Author-email: contact@airbyte.io
-Description-Content-Type: text/markdown
-Requires-Dist: airbyte-cdk
-Requires-Dist: backoff
-Requires-Dist: requests
-Requires-Dist: google-auth-httplib2
-Requires-Dist: google-api-python-client
-Requires-Dist: PyYAML~=6.0
-Requires-Dist: pydantic~=1.9.2
-Requires-Dist: Unidecode
-Provides-Extra: tests
-Requires-Dist: requests-mock~=1.9.3; extra == "tests"
-Requires-Dist: pytest-mock~=3.6.1; extra == "tests"
-Requires-Dist: pytest~=6.1; extra == "tests"
-
-# Pypi Source
-
-This is the repository for the Pypi configuration based source connector.
-For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/pypi).
-
-
-**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/pypi)
-to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_pypi/spec.yaml` file.
-Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
-See `integration_tests/sample_config.json` for a sample config file.
-
-**If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source pypi test creds`
-and place them into `secrets/config.json`.
-
-
-
-**Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**
-```bash
-airbyte-ci connectors --name source-pypi build
-```
-
-An image will be built with the tag `airbyte/source-pypi:dev`.
-
-**Via `docker build`:**
-```bash
-docker build -t airbyte/source-pypi:dev .
-```
-
-Then run any of the connector commands as follows:
-```
-docker run --rm airbyte/source-pypi:dev spec
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-pypi:dev check --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-pypi:dev discover --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-pypi:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
-```
-
-You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
-```bash
-airbyte-ci connectors --name=source-google-sheets test
-```
-
-Customize `acceptance-test-config.yml` file to configure tests. See [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference) for more information.
-If your connector requires to create or destroy resources for use during acceptance tests create fixtures for it and place them inside integration_tests/acceptance.py.
-
-All of your dependencies should go in `setup.py`, NOT `requirements.txt`. The requirements file is only used to connect internal Airbyte dependencies in the monorepo for local development.
-We split dependencies between two groups, dependencies that are:
-* required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
-* required for the testing need to go to `TEST_REQUIREMENTS` list
-
-You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
-1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-google-sheets test`
-2. Bump the connector version in `metadata.yaml`: increment the `dockerImageTag` value. Please follow [semantic versioning for connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#semantic-versioning-for-connectors).
-3. Make sure the `metadata.yaml` content is up to date.
-4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/google-sheets.md`).
-5. Create a Pull Request: use [our PR naming conventions](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#pull-request-title-convention).
-6. Pat yourself on the back for being an awesome contributor.
-7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.

airbyte-source-google-sheets-0.3.14/airbyte_source_google_sheets.egg-info/SOURCES.txt

@@ -1,23 +0,0 @@
-README.md
-setup.cfg
-setup.py
-airbyte_source_google_sheets.egg-info/PKG-INFO
-airbyte_source_google_sheets.egg-info/SOURCES.txt
-airbyte_source_google_sheets.egg-info/dependency_links.txt
-airbyte_source_google_sheets.egg-info/entry_points.txt
-airbyte_source_google_sheets.egg-info/requires.txt
-airbyte_source_google_sheets.egg-info/top_level.txt
-integration_tests/__init__.py
-integration_tests/acceptance.py
-integration_tests/configured_catalog.json
-integration_tests/invalid_config.json
-source_google_sheets/__init__.py
-source_google_sheets/client.py
-source_google_sheets/helpers.py
-source_google_sheets/run.py
-source_google_sheets/source.py
-source_google_sheets/spec.yaml
-source_google_sheets/utils.py
-source_google_sheets/models/__init__.py
-source_google_sheets/models/spreadsheet.py
-source_google_sheets/models/spreadsheet_values.py

airbyte-source-google-sheets-0.3.14/airbyte_source_google_sheets.egg-info/dependency_links.txt

@@ -1 +0,0 @@
-

airbyte-source-google-sheets-0.3.14/airbyte_source_google_sheets.egg-info/entry_points.txt

@@ -1,2 +0,0 @@
-[console_scripts]
-source-google-sheets = source_google_sheets.run:run

airbyte-source-google-sheets-0.3.14/airbyte_source_google_sheets.egg-info/requires.txt

@@ -1,13 +0,0 @@
-airbyte-cdk
-backoff
-requests
-google-auth-httplib2
-google-api-python-client
-PyYAML~=6.0
-pydantic~=1.9.2
-Unidecode
-
-[tests]
-requests-mock~=1.9.3
-pytest-mock~=3.6.1
-pytest~=6.1

airbyte-source-google-sheets-0.3.14/airbyte_source_google_sheets.egg-info/top_level.txt

@@ -1,2 +0,0 @@
-integration_tests
-source_google_sheets

airbyte-source-google-sheets-0.3.14/integration_tests/acceptance.py

@@ -1,14 +0,0 @@
-#
-# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
-#
-
-
-import pytest
-
-pytest_plugins = ("connector_acceptance_test.plugin",)
-
-
-@pytest.fixture(scope="session", autouse=True)
-def connector_setup():
-    """This fixture is a placeholder for external resources that acceptance test might require."""
-    yield

airbyte-source-google-sheets-0.3.14/integration_tests/configured_catalog.json

@@ -1,106 +0,0 @@
-{
-  "streams": [
-    {
-      "stream": {
-        "name": "Sheet1-one-col",
-        "json_schema": {
-          "$schema": "http://json-schema.org/draft-07/schema#",
-          "type": "object",
-          "properties": {
-            "ID": {
-              "type": "string"
-            }
-          }
-        },
-        "supported_sync_modes": ["full_refresh"],
-        "source_defined_cursor": false
-      },
-      "sync_mode": "full_refresh",
-      "destination_sync_mode": "overwrite"
-    },
-    {
-      "stream": {
-        "name": "Sheet2-two-cols",
-        "json_schema": {
-          "$schema": "http://json-schema.org/draft-07/schema#",
-          "type": "object",
-          "properties": {
-            "ID": {
-              "type": "string"
-            },
-            "Name": {
-              "type": "string"
-            }
-          }
-        },
-        "supported_sync_modes": ["full_refresh"],
-        "source_defined_cursor": false
-      },
-      "sync_mode": "full_refresh",
-      "destination_sync_mode": "overwrite"
-    },
-    {
-      "stream": {
-        "name": "Sheet3-two-cols-with-diagram",
-        "json_schema": {
-          "$schema": "http://json-schema.org/draft-07/schema#",
-          "type": "object",
-          "properties": {
-            "ID": {
-              "type": "string"
-            },
-            "Name": {
-              "type": "string"
-            }
-          }
-        },
-        "supported_sync_modes": ["full_refresh"],
-        "source_defined_cursor": false
-      },
-      "sync_mode": "full_refresh",
-      "destination_sync_mode": "overwrite"
-    },
-    {
-      "stream": {
-        "name": "Sheet4-two-cols-no-header",
-        "json_schema": {
-          "$schema": "http://json-schema.org/draft-07/schema#",
-          "type": "object",
-          "properties": {
-            "1": {
-              "type": "string"
-            },
-            "a": {
-              "type": "string"
-            }
-          }
-        },
-        "supported_sync_modes": ["full_refresh"],
-        "source_defined_cursor": false
-      },
-      "sync_mode": "full_refresh",
-      "destination_sync_mode": "overwrite"
-    },
-    {
-      "stream": {
-        "name": "Sheet6-4000-rows",
-        "json_schema": {
-          "$schema": "http://json-schema.org/draft-07/schema#",
-          "type": "object",
-          "properties": {
-            "ID": {
-              "type": "string"
-            },
-            "Name": {
-              "type": "string"
-            }
-          }
-        },
-        "supported_sync_modes": ["full_refresh"],
-        "source_defined_cursor": false
-      },
-      "sync_mode": "full_refresh",
-      "destination_sync_mode": "overwrite"
-    }
-  ]
-}

airbyte-source-google-sheets-0.3.14/integration_tests/invalid_config.json

@@ -1,9 +0,0 @@
-{
-  "spreadsheet_id": "invalid_spreadsheet_id",
-  "credentials": {
-    "auth_type": "Client",
-    "client_id": "invalid_id",
-    "client_secret": "invalid_secret",
-    "refresh_token": "invalid_token"
-  }
-}

airbyte-source-google-sheets-0.3.14/setup.cfg

@@ -1,68 +0,0 @@
-[metadata]
-name = airbyte-source-google-sheets
-version = 0.3.14
-author = Airbyte
-author_email = contact@airbyte.io
-long_description = # Pypi Source
-	
-	This is the repository for the Pypi configuration based source connector.
-	For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/pypi).
-	
-	
-	**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/pypi)
-	to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_pypi/spec.yaml` file.
-	Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
-	See `integration_tests/sample_config.json` for a sample config file.
-	
-	**If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source pypi test creds`
-	and place them into `secrets/config.json`.
-	
-	
-	
-	**Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**
-	```bash
-	airbyte-ci connectors --name source-pypi build
-	```
-	
-	An image will be built with the tag `airbyte/source-pypi:dev`.
-	
-	**Via `docker build`:**
-	```bash
-	docker build -t airbyte/source-pypi:dev .
-	```
-	
-	Then run any of the connector commands as follows:
-	```
-	docker run --rm airbyte/source-pypi:dev spec
-	docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-pypi:dev check --config /secrets/config.json
-	docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-pypi:dev discover --config /secrets/config.json
-	docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-pypi:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
-	```
-	
-	You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
-	```bash
-	airbyte-ci connectors --name=source-google-sheets test
-	```
-	
-	Customize `acceptance-test-config.yml` file to configure tests. See [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference) for more information.
-	If your connector requires to create or destroy resources for use during acceptance tests create fixtures for it and place them inside integration_tests/acceptance.py.
-	
-	All of your dependencies should go in `setup.py`, NOT `requirements.txt`. The requirements file is only used to connect internal Airbyte dependencies in the monorepo for local development.
-	We split dependencies between two groups, dependencies that are:
-	* required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
-	* required for the testing need to go to `TEST_REQUIREMENTS` list
-	
-	You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
-	1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-google-sheets test`
-	2. Bump the connector version in `metadata.yaml`: increment the `dockerImageTag` value. Please follow [semantic versioning for connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#semantic-versioning-for-connectors).
-	3. Make sure the `metadata.yaml` content is up to date.
-	4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/google-sheets.md`).
-	5. Create a Pull Request: use [our PR naming conventions](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#pull-request-title-convention).
-	6. Pat yourself on the back for being an awesome contributor.
-	7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
-long_description_content_type = text/markdown
-
-[egg_info]
-tag_build = 
-tag_date = 0
-

airbyte-source-google-sheets-0.3.14/setup.py

@@ -1,50 +0,0 @@
-#
-# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
-#
-
-
-from setuptools import find_packages, setup
-
-MAIN_REQUIREMENTS = [
-    "airbyte-cdk",
-    "backoff",
-    "requests",
-    "google-auth-httplib2",
-    "google-api-python-client",
-    "PyYAML~=6.0",
-    "pydantic~=1.9.2",
-    "Unidecode",
-]
-
-TEST_REQUIREMENTS = [
-    "requests-mock~=1.9.3",
-    "pytest-mock~=3.6.1",
-    "pytest~=6.1",
-]
-
-setup(
-    description="Source implementation for Google Sheets.",
-    packages=find_packages(),
-    install_requires=MAIN_REQUIREMENTS,
-    package_data={
-        "": [
-            # Include yaml files in the package (if any)
-            "*.yml",
-            "*.yaml",
-            # Include all json files in the package, up to 4 levels deep
-            "*.json",
-            "*/*.json",
-            "*/*/*.json",
-            "*/*/*/*.json",
-            "*/*/*/*/*.json",
-        ]
-    },
-    extras_require={
-        "tests": TEST_REQUIREMENTS,
-    },
-    entry_points={
-        "console_scripts": [
-            "source-google-sheets=source_google_sheets.run:run",
-        ],
-    },
-)