airbyte-source-google-directory 0.2.1__py3-none-any.whl → 0.2.3__py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,114 @@
1
+ Metadata-Version: 2.1
2
+ Name: airbyte-source-google-directory
3
+ Version: 0.2.3
4
+ Summary: Source implementation for Google Directory.
5
+ Home-page: https://airbyte.com
6
+ License: MIT
7
+ Author: Airbyte
8
+ Author-email: contact@airbyte.io
9
+ Requires-Python: >=3.9,<3.12
10
+ Classifier: License :: OSI Approved :: MIT License
11
+ Classifier: Programming Language :: Python :: 3
12
+ Classifier: Programming Language :: Python :: 3.9
13
+ Classifier: Programming Language :: Python :: 3.10
14
+ Classifier: Programming Language :: Python :: 3.11
15
+ Requires-Dist: airbyte-cdk (==0.80.0)
16
+ Requires-Dist: backoff (==1.10.0)
17
+ Requires-Dist: google-api-python-client (==1.12.8)
18
+ Requires-Dist: google-auth-httplib2 (==0.0.4)
19
+ Requires-Dist: google-auth-oauthlib (==0.4.2)
20
+ Project-URL: Documentation, https://docs.airbyte.com/integrations/sources/google-directory
21
+ Project-URL: Repository, https://github.com/airbytehq/airbyte
22
+ Description-Content-Type: text/markdown
23
+
24
+ # Google-Directory source connector
25
+
26
+
27
+ This is the repository for the Google-Directory source connector, written in Python.
28
+ For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/google-directory).
29
+
30
+ ## Local development
31
+
32
+ ### Prerequisites
33
+ * Python (~=3.9)
34
+ * Poetry (~=1.7) - installation instructions [here](https://python-poetry.org/docs/#installation)
35
+
36
+
37
+ ### Installing the connector
38
+ From this connector directory, run:
39
+ ```bash
40
+ poetry install --with dev
41
+ ```
42
+
43
+
44
+ ### Create credentials
45
+ **If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.com/integrations/sources/google-directory)
46
+ to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_google_directory/spec.yaml` file.
47
+ Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
48
+ See `sample_files/sample_config.json` for a sample config file.
49
+
50
+
51
+ ### Locally running the connector
52
+ ```
53
+ poetry run source-google-directory spec
54
+ poetry run source-google-directory check --config secrets/config.json
55
+ poetry run source-google-directory discover --config secrets/config.json
56
+ poetry run source-google-directory read --config secrets/config.json --catalog sample_files/configured_catalog.json
57
+ ```
58
+
59
+ ### Running unit tests
60
+ To run unit tests locally, from the connector directory run:
61
+ ```
62
+ poetry run pytest unit_tests
63
+ ```
64
+
65
+ ### Building the docker image
66
+ 1. Install [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md)
67
+ 2. Run the following command to build the docker image:
68
+ ```bash
69
+ airbyte-ci connectors --name=source-google-directory build
70
+ ```
71
+
72
+ An image will be available on your host with the tag `airbyte/source-google-directory:dev`.
73
+
74
+
75
+ ### Running as a docker container
76
+ Then run any of the connector commands as follows:
77
+ ```
78
+ docker run --rm airbyte/source-google-directory:dev spec
79
+ docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-google-directory:dev check --config /secrets/config.json
80
+ docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-google-directory:dev discover --config /secrets/config.json
81
+ 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
82
+ ```
83
+
84
+ ### Running our CI test suite
85
+ You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
86
+ ```bash
87
+ airbyte-ci connectors --name=source-google-directory test
88
+ ```
89
+
90
+ ### Customizing acceptance Tests
91
+ 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.
92
+ 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.
93
+
94
+ ### Dependency Management
95
+ All of your dependencies should be managed via Poetry.
96
+ To add a new dependency, run:
97
+ ```bash
98
+ poetry add <package-name>
99
+ ```
100
+
101
+ Please commit the changes to `pyproject.toml` and `poetry.lock` files.
102
+
103
+ ## Publishing a new version of the connector
104
+ You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
105
+ 1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-google-directory test`
106
+ 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)):
107
+ - bump the `dockerImageTag` value in in `metadata.yaml`
108
+ - bump the `version` value in `pyproject.toml`
109
+ 3. Make sure the `metadata.yaml` content is up to date.
110
+ 4. Make sure the connector documentation and its changelog is up to date (`docs/integrations/sources/google-directory.md`).
111
+ 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).
112
+ 6. Pat yourself on the back for being an awesome contributor.
113
+ 7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
114
+ 8. Once your PR is merged, the new version of the connector will be automatically published to Docker Hub and our connector registry.
@@ -0,0 +1,14 @@
1
+ source_google_directory/__init__.py,sha256=nyTWRMLy_XY30WnneaB81SxdmV03gO85FfPnWWQlpIo,140
2
+ source_google_directory/api.py,sha256=jiEi5SI7q-15T_JdN7wzghxPiz_yXq6xQCBJmp84olQ,4934
3
+ source_google_directory/client.py,sha256=9VTFMOeIoJ_BwjESLVatR6vsc55AekkjzZECA-tkM7M,1565
4
+ source_google_directory/run.py,sha256=VgZRQrOHkVa1egt6nagTwWG5N-xoIFr6DRI6-57Hxoc,258
5
+ source_google_directory/schemas/group_members.json,sha256=xXupERXB7X7JmozWR36genWxmPurMR2SuKC37JHUSkg,480
6
+ source_google_directory/schemas/groups.json,sha256=beEqkaJKAS87mGmov4zjynCnZi5a6MMHZ7c_qeL6NKM,807
7
+ source_google_directory/schemas/users.json,sha256=vc_A6SA2ya7l8HtyfohEZP-O-CAjkG-3XUkZNfExyUA,6281
8
+ source_google_directory/source.py,sha256=JrZGcqusFfJH9FdShTuHHaUqsAEEWEMIwhCN56Ws1rM,226
9
+ source_google_directory/spec.json,sha256=5ctMlUUJnl3iRnzyxgpeS9b197oDaPB9m8kUalC_IXM,3400
10
+ source_google_directory/utils.py,sha256=jiqxFTyM02XxfUSVovHf-qvWPzeX9LaMGIWuSULZNBo,263
11
+ airbyte_source_google_directory-0.2.3.dist-info/METADATA,sha256=5-uXVZHR1hE27g4VIJ1170KJycet99CYq_n6WiTcEGE,5587
12
+ airbyte_source_google_directory-0.2.3.dist-info/WHEEL,sha256=sP946D7jFCHeNz5Iq4fL4Lu-PrWrFsgfLXbbkciIZwg,88
13
+ airbyte_source_google_directory-0.2.3.dist-info/entry_points.txt,sha256=I44bbF13B_FO3AJX6HMDwTyoIb8Qv6CIR06m_CcOnis,75
14
+ airbyte_source_google_directory-0.2.3.dist-info/RECORD,,
@@ -1,5 +1,4 @@
1
1
  Wheel-Version: 1.0
2
- Generator: bdist_wheel (0.42.0)
2
+ Generator: poetry-core 1.9.0
3
3
  Root-Is-Purelib: true
4
4
  Tag: py3-none-any
5
-
@@ -0,0 +1,3 @@
1
+ [console_scripts]
2
+ source-google-directory=source_google_directory.run:run
3
+
@@ -1,103 +0,0 @@
1
- Metadata-Version: 2.1
2
- Name: airbyte-source-google-directory
3
- Version: 0.2.1
4
- Summary: Source implementation for Google Directory.
5
- Author: Airbyte
6
- Author-email: contact@airbyte.io
7
- Description-Content-Type: text/markdown
8
- Requires-Dist: airbyte-cdk ~=0.1
9
- Requires-Dist: google-api-python-client ==1.12.8
10
- Requires-Dist: google-auth-httplib2 ==0.0.4
11
- Requires-Dist: google-auth-oauthlib ==0.4.2
12
- Requires-Dist: backoff ==1.10.0
13
- Provides-Extra: tests
14
- Requires-Dist: requests-mock ~=1.9.3 ; extra == 'tests'
15
- Requires-Dist: pytest ~=6.1 ; extra == 'tests'
16
- Requires-Dist: pytest-mock ~=3.6.1 ; extra == 'tests'
17
-
18
- # Freshsales Source
19
-
20
- This is the repository for the Freshsales source connector, written in Python.
21
- For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/freshsales).
22
-
23
-
24
- **To iterate on this connector, make sure to complete this prerequisites section.**
25
-
26
-
27
- From this connector directory, create a virtual environment:
28
- ```
29
- python -m venv .venv
30
- ```
31
-
32
- This will generate a virtualenv for this module in `.venv/`. Make sure this venv is active in your
33
- development environment of choice. To activate it from the terminal, run:
34
- ```
35
- source .venv/bin/activate
36
- pip install -r requirements.txt
37
- pip install '.[tests]'
38
- ```
39
- If you are in an IDE, follow your IDE's instructions to activate the virtualenv.
40
-
41
- Note that while we are installing dependencies from `requirements.txt`, you should only edit `setup.py` for your dependencies. `requirements.txt` is
42
- used for editable installs (`pip install -e`) to pull in Python dependencies from the monorepo and will call `setup.py`.
43
- 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
44
- should work as you expect.
45
-
46
- **If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/freshsales)
47
- to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_freshsales/spec.json` file.
48
- Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
49
- See `integration_tests/sample_config.json` for a sample config file.
50
-
51
- **If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source freshsales test creds`
52
- and place them into `secrets/config.json`.
53
-
54
- ```
55
- python main.py spec
56
- python main.py check --config secrets/config.json
57
- python main.py discover --config secrets/config.json
58
- python main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.json
59
- ```
60
-
61
-
62
-
63
- **Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**
64
- ```bash
65
- airbyte-ci connectors --name source-freshsales build
66
- ```
67
-
68
- An image will be built with the tag `airbyte/source-freshsales:dev`.
69
-
70
- **Via `docker build`:**
71
- ```bash
72
- docker build -t airbyte/source-freshsales:dev .
73
- ```
74
-
75
- Then run any of the connector commands as follows:
76
- ```
77
- docker run --rm airbyte/source-freshsales:dev spec
78
- docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-freshsales:dev check --config /secrets/config.json
79
- docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-freshsales:dev discover --config /secrets/config.json
80
- 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
81
- ```
82
-
83
- You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
84
- ```bash
85
- airbyte-ci connectors --name=source-google-directory test
86
- ```
87
-
88
- 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.
89
- 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.
90
-
91
- 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.
92
- We split dependencies between two groups, dependencies that are:
93
- * required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
94
- * required for the testing need to go to `TEST_REQUIREMENTS` list
95
-
96
- You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
97
- 1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-google-directory test`
98
- 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).
99
- 3. Make sure the `metadata.yaml` content is up to date.
100
- 4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/google-directory.md`).
101
- 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).
102
- 6. Pat yourself on the back for being an awesome contributor.
103
- 7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
@@ -1,22 +0,0 @@
1
- integration_tests/__init__.py,sha256=4Hw-PX1-VgESLF16cDdvuYCzGJtHntThLF4qIiULWeo,61
2
- integration_tests/acceptance.py,sha256=VpQhkCpkovNSs0uLNh6iAdJ0WY-gYg0FbSBl8te_D0A,314
3
- integration_tests/configured_catalog.json,sha256=zwWHL_CY3Ad4zRIrYTbpv9oCc1G3IP9szj56nLkM9Js,1045
4
- integration_tests/invalid_config.json,sha256=2LBkBetpqSobJSmzk5jNKV9swKxS8Zd7gYH-UWUxy4w,60
5
- integration_tests/invalid_config_oauth.json,sha256=vtZtCbna-VFDthslYtyGZmgoCUog8z9X7_xImkv5468,162
6
- integration_tests/sample_config.json,sha256=QEPAy-Seg3N4_WhX5O_TS4wvEkkm2LHpSibzzY1XdWo,131
7
- integration_tests/sample_config_oauth.json,sha256=587Pe1jPq2ABpPH_BrD207MWeLph5E8TcpGmAaWb1ZA,138
8
- source_google_directory/__init__.py,sha256=nyTWRMLy_XY30WnneaB81SxdmV03gO85FfPnWWQlpIo,140
9
- source_google_directory/api.py,sha256=jiEi5SI7q-15T_JdN7wzghxPiz_yXq6xQCBJmp84olQ,4934
10
- source_google_directory/client.py,sha256=9VTFMOeIoJ_BwjESLVatR6vsc55AekkjzZECA-tkM7M,1565
11
- source_google_directory/run.py,sha256=VgZRQrOHkVa1egt6nagTwWG5N-xoIFr6DRI6-57Hxoc,258
12
- source_google_directory/source.py,sha256=JrZGcqusFfJH9FdShTuHHaUqsAEEWEMIwhCN56Ws1rM,226
13
- source_google_directory/spec.json,sha256=5ctMlUUJnl3iRnzyxgpeS9b197oDaPB9m8kUalC_IXM,3400
14
- source_google_directory/utils.py,sha256=jiqxFTyM02XxfUSVovHf-qvWPzeX9LaMGIWuSULZNBo,263
15
- source_google_directory/schemas/group_members.json,sha256=xXupERXB7X7JmozWR36genWxmPurMR2SuKC37JHUSkg,480
16
- source_google_directory/schemas/groups.json,sha256=beEqkaJKAS87mGmov4zjynCnZi5a6MMHZ7c_qeL6NKM,807
17
- source_google_directory/schemas/users.json,sha256=vc_A6SA2ya7l8HtyfohEZP-O-CAjkG-3XUkZNfExyUA,6281
18
- airbyte_source_google_directory-0.2.1.dist-info/METADATA,sha256=o0q-BOkiTqhZGXq6odDREqN5Sw8JIH2H_Kfq_47zOl4,5650
19
- airbyte_source_google_directory-0.2.1.dist-info/WHEEL,sha256=oiQVh_5PnQM0E3gPdiz09WCNmwiHDMaGer_elqB3coM,92
20
- airbyte_source_google_directory-0.2.1.dist-info/entry_points.txt,sha256=aDK2F06TBzPiuPd9JC2kVkFBqI4epJgtlNoaSH3BqNE,76
21
- airbyte_source_google_directory-0.2.1.dist-info/top_level.txt,sha256=hyddsYv2rZ2GvbDaKGMaBLA9tAope2H9dKajGyT-f64,42
22
- airbyte_source_google_directory-0.2.1.dist-info/RECORD,,
@@ -1,2 +0,0 @@
1
- [console_scripts]
2
- source-google-directory = source_google_directory.run:run
@@ -1,2 +0,0 @@
1
- integration_tests
2
- source_google_directory
@@ -1,3 +0,0 @@
1
- #
2
- # Copyright (c) 2023 Airbyte, Inc., all rights reserved.
3
- #
@@ -1,14 +0,0 @@
1
- #
2
- # Copyright (c) 2023 Airbyte, Inc., all rights reserved.
3
- #
4
-
5
-
6
- import pytest
7
-
8
- pytest_plugins = ("connector_acceptance_test.plugin",)
9
-
10
-
11
- @pytest.fixture(scope="session", autouse=True)
12
- def connector_setup():
13
- """This fixture is a placeholder for external resources that acceptance test might require."""
14
- yield
@@ -1,40 +0,0 @@
1
- {
2
- "streams": [
3
- {
4
- "stream": {
5
- "name": "users",
6
- "json_schema": {},
7
- "supported_sync_modes": ["full_refresh"],
8
- "source_defined_cursor": false,
9
- "source_defined_primary_key": [["id"]]
10
- },
11
- "sync_mode": "full_refresh",
12
- "destination_sync_mode": "overwrite",
13
- "primary_key": [["id"]]
14
- },
15
- {
16
- "stream": {
17
- "name": "groups",
18
- "json_schema": {},
19
- "supported_sync_modes": ["full_refresh"],
20
- "source_defined_cursor": false,
21
- "source_defined_primary_key": [["id"]]
22
- },
23
- "sync_mode": "full_refresh",
24
- "destination_sync_mode": "overwrite",
25
- "primary_key": [["id"]]
26
- },
27
- {
28
- "stream": {
29
- "name": "group_members",
30
- "json_schema": {},
31
- "supported_sync_modes": ["full_refresh"],
32
- "source_defined_cursor": false,
33
- "source_defined_primary_key": [["id"]]
34
- },
35
- "sync_mode": "full_refresh",
36
- "destination_sync_mode": "overwrite",
37
- "primary_key": [["id"]]
38
- }
39
- ]
40
- }
@@ -1,4 +0,0 @@
1
- {
2
- "credentials_json": "{}",
3
- "email": "test@test.test"
4
- }
@@ -1,7 +0,0 @@
1
- {
2
- "credentials": {
3
- "client_id": "<invalid_client_id>",
4
- "client_secret": "<invalid_client_secret>",
5
- "refresh_token": "<invalid_refresh_token>"
6
- }
7
- }
@@ -1,6 +0,0 @@
1
- {
2
- "credentials": {
3
- "credentials_json": "<The contents of the JSON service account key>",
4
- "email": "test@test.test"
5
- }
6
- }
@@ -1,7 +0,0 @@
1
- {
2
- "credentials": {
3
- "client_id": "<Client ID>",
4
- "client_secret": "<Client secret>",
5
- "refresh_token": "<Refresh token>"
6
- }
7
- }