airbyte-source-google-directory 0.2.1__tar.gz → 0.2.2__tar.gz

airbyte_source_google_directory-0.2.2/PKG-INFO

@@ -0,0 +1,114 @@
+Metadata-Version: 2.1
+Name: airbyte-source-google-directory
+Version: 0.2.2
+Summary: Source implementation for Google Directory.
+Home-page: https://airbyte.com
+License: MIT
+Author: Airbyte
+Author-email: contact@airbyte.io
+Requires-Python: >=3.9,<3.12
+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
+Requires-Dist: airbyte-cdk (==0.80.0)
+Requires-Dist: backoff (==1.10.0)
+Requires-Dist: google-api-python-client (==1.12.8)
+Requires-Dist: google-auth-httplib2 (==0.0.4)
+Requires-Dist: google-auth-oauthlib (==0.4.2)
+Project-URL: Documentation, https://docs.airbyte.com/integrations/sources/google-directory
+Project-URL: Repository, https://github.com/airbytehq/airbyte
+Description-Content-Type: text/markdown
+
+# Google-Directory source connector
+
+
+This is the repository for the Google-Directory 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-directory).
+
+## 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-directory)
+to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_google_directory/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-directory spec
+poetry run source-google-directory check --config secrets/config.json
+poetry run source-google-directory discover --config secrets/config.json
+poetry run source-google-directory 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-directory build
+```
+
+An image will be available on your host with the tag `airbyte/source-google-directory:dev`.
+
+
+### Running as a docker container
+Then run any of the connector commands as follows:
+```
+docker run --rm airbyte/source-google-directory:dev spec
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-google-directory:dev check --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-google-directory:dev discover --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-google-directory: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-directory 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-directory 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-directory.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_directory-0.2.2/README.md

@@ -0,0 +1,91 @@
+# Google-Directory source connector
+
+
+This is the repository for the Google-Directory 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-directory).
+
+## 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-directory)
+to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_google_directory/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-directory spec
+poetry run source-google-directory check --config secrets/config.json
+poetry run source-google-directory discover --config secrets/config.json
+poetry run source-google-directory 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-directory build
+```
+
+An image will be available on your host with the tag `airbyte/source-google-directory:dev`.
+
+
+### Running as a docker container
+Then run any of the connector commands as follows:
+```
+docker run --rm airbyte/source-google-directory:dev spec
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-google-directory:dev check --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-google-directory:dev discover --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-google-directory: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-directory 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-directory 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-directory.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_directory-0.2.2/pyproject.toml

@@ -0,0 +1,37 @@
+[build-system]
+requires = [
+    "poetry-core>=1.0.0",
+]
+build-backend = "poetry.core.masonry.api"
+
+[tool.poetry]
+version = "0.2.2"
+name = "airbyte-source-google-directory"
+description = "Source implementation for Google Directory."
+authors = [
+    "Airbyte <contact@airbyte.io>",
+]
+license = "MIT"
+readme = "README.md"
+documentation = "https://docs.airbyte.com/integrations/sources/google-directory"
+homepage = "https://airbyte.com"
+repository = "https://github.com/airbytehq/airbyte"
+packages = [
+    { include = "source_google_directory" },
+]
+
+[tool.poetry.dependencies]
+python = "^3.9,<3.12"
+google-auth-oauthlib = "==0.4.2"
+google-auth-httplib2 = "==0.0.4"
+google-api-python-client = "==1.12.8"
+airbyte-cdk = "0.80.0"
+backoff = "==1.10.0"
+
+[tool.poetry.scripts]
+source-google-directory = "source_google_directory.run:run"
+
+[tool.poetry.group.dev.dependencies]
+pytest-mock = "^3.6.1"
+requests-mock = "^1.9.3"
+pytest = "^6.1"

airbyte-source-google-directory-0.2.1/PKG-INFO

@@ -1,103 +0,0 @@
-Metadata-Version: 2.1
-Name: airbyte-source-google-directory
-Version: 0.2.1
-Summary: Source implementation for Google Directory.
-Author: Airbyte
-Author-email: contact@airbyte.io
-Description-Content-Type: text/markdown
-Requires-Dist: airbyte-cdk~=0.1
-Requires-Dist: google-api-python-client==1.12.8
-Requires-Dist: google-auth-httplib2==0.0.4
-Requires-Dist: google-auth-oauthlib==0.4.2
-Requires-Dist: backoff==1.10.0
-Provides-Extra: tests
-Requires-Dist: requests-mock~=1.9.3; extra == "tests"
-Requires-Dist: pytest~=6.1; extra == "tests"
-Requires-Dist: pytest-mock~=3.6.1; extra == "tests"
-
-# Freshsales Source
-
-This is the repository for the Freshsales source connector, written in Python.
-For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/freshsales).
-
-
-**To iterate on this connector, make sure to complete this prerequisites section.**
-
-
-From this connector directory, create a virtual environment:
-```
-python -m venv .venv
-```
-
-This will generate a virtualenv for this module in `.venv/`. Make sure this venv is active in your
-development environment of choice. To activate it from the terminal, run:
-```
-source .venv/bin/activate
-pip install -r requirements.txt
-pip install '.[tests]'
-```
-If you are in an IDE, follow your IDE's instructions to activate the virtualenv.
-
-Note that while we are installing dependencies from `requirements.txt`, you should only edit `setup.py` for your dependencies. `requirements.txt` is
-used for editable installs (`pip install -e`) to pull in Python dependencies from the monorepo and will call `setup.py`.
-If this is mumbo jumbo to you, don't worry about it, just put your deps in `setup.py` but install using `pip install -r requirements.txt` and everything
-should work as you expect.
-
-**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/freshsales)
-to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_freshsales/spec.json` 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 freshsales test creds`
-and place them into `secrets/config.json`.
-
-```
-python main.py spec
-python main.py check --config secrets/config.json
-python main.py discover --config secrets/config.json
-python main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.json
-```
-
-
-
-**Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**
-```bash
-airbyte-ci connectors --name source-freshsales build
-```
-
-An image will be built with the tag `airbyte/source-freshsales:dev`.
-
-**Via `docker build`:**
-```bash
-docker build -t airbyte/source-freshsales:dev .
-```
-
-Then run any of the connector commands as follows:
-```
-docker run --rm airbyte/source-freshsales:dev spec
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-freshsales:dev check --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-freshsales:dev discover --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-freshsales: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-directory 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-directory 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-directory.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-directory-0.2.1/README.md

@@ -1,100 +0,0 @@
-# Freshsales Source
-
-This is the repository for the Freshsales source connector, written in Python.
-For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/freshsales).
-
-## Local development
-
-### Prerequisites
-**To iterate on this connector, make sure to complete this prerequisites section.**
-
-#### Minimum Python version required `= 3.7.0`
-
-#### Build & Activate Virtual Environment and install dependencies
-From this connector directory, create a virtual environment:
-```
-python -m venv .venv
-```
-
-This will generate a virtualenv for this module in `.venv/`. Make sure this venv is active in your
-development environment of choice. To activate it from the terminal, run:
-```
-source .venv/bin/activate
-pip install -r requirements.txt
-pip install '.[tests]'
-```
-If you are in an IDE, follow your IDE's instructions to activate the virtualenv.
-
-Note that while we are installing dependencies from `requirements.txt`, you should only edit `setup.py` for your dependencies. `requirements.txt` is
-used for editable installs (`pip install -e`) to pull in Python dependencies from the monorepo and will call `setup.py`.
-If this is mumbo jumbo to you, don't worry about it, just put your deps in `setup.py` but install using `pip install -r requirements.txt` and everything
-should work as you expect.
-
-#### Create credentials
-**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/freshsales)
-to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_freshsales/spec.json` 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 freshsales test creds`
-and place them into `secrets/config.json`.
-
-### Locally running the connector
-```
-python main.py spec
-python main.py check --config secrets/config.json
-python main.py discover --config secrets/config.json
-python main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.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-freshsales build
-```
-
-An image will be built with the tag `airbyte/source-freshsales:dev`.
-
-**Via `docker build`:**
-```bash
-docker build -t airbyte/source-freshsales:dev .
-```
-
-#### Run
-Then run any of the connector commands as follows:
-```
-docker run --rm airbyte/source-freshsales:dev spec
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-freshsales:dev check --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-freshsales:dev discover --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-freshsales: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-directory 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-directory 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-directory.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-directory-0.2.1/airbyte_source_google_directory.egg-info/PKG-INFO

@@ -1,103 +0,0 @@
-Metadata-Version: 2.1
-Name: airbyte-source-google-directory
-Version: 0.2.1
-Summary: Source implementation for Google Directory.
-Author: Airbyte
-Author-email: contact@airbyte.io
-Description-Content-Type: text/markdown
-Requires-Dist: airbyte-cdk~=0.1
-Requires-Dist: google-api-python-client==1.12.8
-Requires-Dist: google-auth-httplib2==0.0.4
-Requires-Dist: google-auth-oauthlib==0.4.2
-Requires-Dist: backoff==1.10.0
-Provides-Extra: tests
-Requires-Dist: requests-mock~=1.9.3; extra == "tests"
-Requires-Dist: pytest~=6.1; extra == "tests"
-Requires-Dist: pytest-mock~=3.6.1; extra == "tests"
-
-# Freshsales Source
-
-This is the repository for the Freshsales source connector, written in Python.
-For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/freshsales).
-
-
-**To iterate on this connector, make sure to complete this prerequisites section.**
-
-
-From this connector directory, create a virtual environment:
-```
-python -m venv .venv
-```
-
-This will generate a virtualenv for this module in `.venv/`. Make sure this venv is active in your
-development environment of choice. To activate it from the terminal, run:
-```
-source .venv/bin/activate
-pip install -r requirements.txt
-pip install '.[tests]'
-```
-If you are in an IDE, follow your IDE's instructions to activate the virtualenv.
-
-Note that while we are installing dependencies from `requirements.txt`, you should only edit `setup.py` for your dependencies. `requirements.txt` is
-used for editable installs (`pip install -e`) to pull in Python dependencies from the monorepo and will call `setup.py`.
-If this is mumbo jumbo to you, don't worry about it, just put your deps in `setup.py` but install using `pip install -r requirements.txt` and everything
-should work as you expect.
-
-**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/freshsales)
-to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_freshsales/spec.json` 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 freshsales test creds`
-and place them into `secrets/config.json`.
-
-```
-python main.py spec
-python main.py check --config secrets/config.json
-python main.py discover --config secrets/config.json
-python main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.json
-```
-
-
-
-**Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**
-```bash
-airbyte-ci connectors --name source-freshsales build
-```
-
-An image will be built with the tag `airbyte/source-freshsales:dev`.
-
-**Via `docker build`:**
-```bash
-docker build -t airbyte/source-freshsales:dev .
-```
-
-Then run any of the connector commands as follows:
-```
-docker run --rm airbyte/source-freshsales:dev spec
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-freshsales:dev check --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-freshsales:dev discover --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-freshsales: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-directory 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-directory 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-directory.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-directory-0.2.1/airbyte_source_google_directory.egg-info/SOURCES.txt

@@ -1,26 +0,0 @@
-README.md
-setup.cfg
-setup.py
-airbyte_source_google_directory.egg-info/PKG-INFO
-airbyte_source_google_directory.egg-info/SOURCES.txt
-airbyte_source_google_directory.egg-info/dependency_links.txt
-airbyte_source_google_directory.egg-info/entry_points.txt
-airbyte_source_google_directory.egg-info/requires.txt
-airbyte_source_google_directory.egg-info/top_level.txt
-integration_tests/__init__.py
-integration_tests/acceptance.py
-integration_tests/configured_catalog.json
-integration_tests/invalid_config.json
-integration_tests/invalid_config_oauth.json
-integration_tests/sample_config.json
-integration_tests/sample_config_oauth.json
-source_google_directory/__init__.py
-source_google_directory/api.py
-source_google_directory/client.py
-source_google_directory/run.py
-source_google_directory/source.py
-source_google_directory/spec.json
-source_google_directory/utils.py
-source_google_directory/schemas/group_members.json
-source_google_directory/schemas/groups.json
-source_google_directory/schemas/users.json

airbyte-source-google-directory-0.2.1/airbyte_source_google_directory.egg-info/dependency_links.txt

@@ -1 +0,0 @@
-

airbyte-source-google-directory-0.2.1/airbyte_source_google_directory.egg-info/entry_points.txt

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

airbyte-source-google-directory-0.2.1/airbyte_source_google_directory.egg-info/requires.txt

@@ -1,10 +0,0 @@
-airbyte-cdk~=0.1
-google-api-python-client==1.12.8
-google-auth-httplib2==0.0.4
-google-auth-oauthlib==0.4.2
-backoff==1.10.0
-
-[tests]
-requests-mock~=1.9.3
-pytest~=6.1
-pytest-mock~=3.6.1

airbyte-source-google-directory-0.2.1/airbyte_source_google_directory.egg-info/top_level.txt

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

airbyte-source-google-directory-0.2.1/integration_tests/__init__.py

@@ -1,3 +0,0 @@
-#
-# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
-#

airbyte-source-google-directory-0.2.1/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-directory-0.2.1/integration_tests/configured_catalog.json

@@ -1,40 +0,0 @@
-{
-  "streams": [
-    {
-      "stream": {
-        "name": "users",
-        "json_schema": {},
-        "supported_sync_modes": ["full_refresh"],
-        "source_defined_cursor": false,
-        "source_defined_primary_key": [["id"]]
-      },
-      "sync_mode": "full_refresh",
-      "destination_sync_mode": "overwrite",
-      "primary_key": [["id"]]
-    },
-    {
-      "stream": {
-        "name": "groups",
-        "json_schema": {},
-        "supported_sync_modes": ["full_refresh"],
-        "source_defined_cursor": false,
-        "source_defined_primary_key": [["id"]]
-      },
-      "sync_mode": "full_refresh",
-      "destination_sync_mode": "overwrite",
-      "primary_key": [["id"]]
-    },
-    {
-      "stream": {
-        "name": "group_members",
-        "json_schema": {},
-        "supported_sync_modes": ["full_refresh"],
-        "source_defined_cursor": false,
-        "source_defined_primary_key": [["id"]]
-      },
-      "sync_mode": "full_refresh",
-      "destination_sync_mode": "overwrite",
-      "primary_key": [["id"]]
-    }
-  ]
-}

airbyte-source-google-directory-0.2.1/integration_tests/invalid_config.json

@@ -1,4 +0,0 @@
-{
-  "credentials_json": "{}",
-  "email": "test@test.test"
-}

airbyte-source-google-directory-0.2.1/integration_tests/invalid_config_oauth.json

@@ -1,7 +0,0 @@
-{
-  "credentials": {
-    "client_id": "<invalid_client_id>",
-    "client_secret": "<invalid_client_secret>",
-    "refresh_token": "<invalid_refresh_token>"
-  }
-}

airbyte-source-google-directory-0.2.1/integration_tests/sample_config.json

@@ -1,6 +0,0 @@
-{
-  "credentials": {
-    "credentials_json": "<The contents of the JSON service account key>",
-    "email": "test@test.test"
-  }
-}

airbyte-source-google-directory-0.2.1/integration_tests/sample_config_oauth.json

@@ -1,7 +0,0 @@
-{
-  "credentials": {
-    "client_id": "<Client ID>",
-    "client_secret": "<Client secret>",
-    "refresh_token": "<Refresh token>"
-  }
-}

airbyte-source-google-directory-0.2.1/setup.cfg

@@ -1,97 +0,0 @@
-[metadata]
-name = airbyte-source-google-directory
-version = 0.2.1
-author = Airbyte
-author_email = contact@airbyte.io
-long_description = # Freshsales Source
-	
-	This is the repository for the Freshsales source connector, written in Python.
-	For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/freshsales).
-	
-	
-	**To iterate on this connector, make sure to complete this prerequisites section.**
-	
-	
-	From this connector directory, create a virtual environment:
-	```
-	python -m venv .venv
-	```
-	
-	This will generate a virtualenv for this module in `.venv/`. Make sure this venv is active in your
-	development environment of choice. To activate it from the terminal, run:
-	```
-	source .venv/bin/activate
-	pip install -r requirements.txt
-	pip install '.[tests]'
-	```
-	If you are in an IDE, follow your IDE's instructions to activate the virtualenv.
-	
-	Note that while we are installing dependencies from `requirements.txt`, you should only edit `setup.py` for your dependencies. `requirements.txt` is
-	used for editable installs (`pip install -e`) to pull in Python dependencies from the monorepo and will call `setup.py`.
-	If this is mumbo jumbo to you, don't worry about it, just put your deps in `setup.py` but install using `pip install -r requirements.txt` and everything
-	should work as you expect.
-	
-	**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/freshsales)
-	to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_freshsales/spec.json` 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 freshsales test creds`
-	and place them into `secrets/config.json`.
-	
-	```
-	python main.py spec
-	python main.py check --config secrets/config.json
-	python main.py discover --config secrets/config.json
-	python main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.json
-	```
-	
-	
-	
-	**Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**
-	```bash
-	airbyte-ci connectors --name source-freshsales build
-	```
-	
-	An image will be built with the tag `airbyte/source-freshsales:dev`.
-	
-	**Via `docker build`:**
-	```bash
-	docker build -t airbyte/source-freshsales:dev .
-	```
-	
-	Then run any of the connector commands as follows:
-	```
-	docker run --rm airbyte/source-freshsales:dev spec
-	docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-freshsales:dev check --config /secrets/config.json
-	docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-freshsales:dev discover --config /secrets/config.json
-	docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-freshsales: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-directory 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-directory 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-directory.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-directory-0.2.1/setup.py

@@ -1,47 +0,0 @@
-#
-# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
-#
-
-
-from setuptools import find_packages, setup
-
-MAIN_REQUIREMENTS = [
-    "airbyte-cdk~=0.1",
-    "google-api-python-client==1.12.8",
-    "google-auth-httplib2==0.0.4",
-    "google-auth-oauthlib==0.4.2",
-    "backoff==1.10.0",
-]
-
-TEST_REQUIREMENTS = [
-    "requests-mock~=1.9.3",
-    "pytest~=6.1",
-    "pytest-mock~=3.6.1",
-]
-
-setup(
-    entry_points={
-        "console_scripts": [
-            "source-google-directory=source_google_directory.run:run",
-        ],
-    },
-    description="Source implementation for Google Directory.",
-    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,
-    },
-)