You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#### Build & Activate Virtual Environment and install dependencies
14
-
From this connector directory, create a virtual environment:
15
-
```
16
-
python -m venv .venv
17
-
```
18
13
19
-
This will generate a virtualenv for this module in `.venv/`. Make sure this venv is active in your
20
-
development environment of choice. To activate it from the terminal, run:
21
-
```
22
-
source .venv/bin/activate
23
-
pip install -r requirements.txt
24
-
pip install '.[tests]'
14
+
### Installing the connector
15
+
From this connector directory, run:
16
+
```bash
17
+
poetry install --with dev
25
18
```
26
-
If you are in an IDE, follow your IDE's instructions to activate the virtualenv.
27
19
28
-
Note that while we are installing dependencies from `requirements.txt`, you should only edit `setup.py` for your dependencies. `requirements.txt` is
29
-
used for editable installs (`pip install -e`) to pull in Python dependencies from the monorepo and will call `setup.py`.
30
-
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
31
-
should work as you expect.
32
20
33
-
####Create credentials
34
-
**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/google-drive)
35
-
to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_google_drive/spec.json` file.
21
+
### Create credentials
22
+
**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.com/integrations/sources/google-drive)
23
+
to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_google_drive/spec.yaml` file.
36
24
Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
37
-
See `integration_tests/sample_config.json` for a sample config file.
25
+
See `sample_files/sample_config.json` for a sample config file.
38
26
39
-
**If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source google-drive test creds`
You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
77
63
```bash
78
64
airbyte-ci connectors --name=source-google-drive test
79
65
```
80
66
81
67
### Customizing acceptance Tests
82
-
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.
68
+
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.
83
69
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.
84
70
85
-
## Dependency Management
86
-
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.
87
-
We split dependencies between two groups, dependencies that are:
88
-
* required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
89
-
* required for the testing need to go to `TEST_REQUIREMENTS` list
71
+
### Dependency Management
72
+
All of your dependencies should be managed via Poetry.
73
+
To add a new dependency, run:
74
+
```bash
75
+
poetry add <package-name>
76
+
```
77
+
78
+
Please commit the changes to `pyproject.toml` and `poetry.lock` files.
90
79
91
-
###Publishing a new version of the connector
80
+
## Publishing a new version of the connector
92
81
You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
93
82
1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-google-drive test`
94
-
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).
83
+
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)):
84
+
- bump the `dockerImageTag` value in in `metadata.yaml`
85
+
- bump the `version` value in `pyproject.toml`
95
86
3. Make sure the `metadata.yaml` content is up to date.
96
-
4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/google-drive.md`).
87
+
4. Make sure the connector documentation and its changelog is up to date (`docs/integrations/sources/google-drive.md`).
97
88
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).
98
89
6. Pat yourself on the back for being an awesome contributor.
99
90
7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
100
-
91
+
8. Once your PR is merged, the new version of the connector will be automatically published to Docker Hub and our connector registry.
Copy file name to clipboardExpand all lines: airbyte-integrations/connectors/source-google-drive/integration_tests/spec.json
+16-10
Original file line number
Diff line number
Diff line change
@@ -31,9 +31,9 @@
31
31
},
32
32
"globs": {
33
33
"title": "Globs",
34
+
"description": "The pattern used to specify which files should be selected from the file system. For more information on glob pattern matching look <a href=\"https://en.wikipedia.org/wiki/Glob_(programming)\">here</a>.",
34
35
"default": ["**"],
35
36
"order": 1,
36
-
"description": "The pattern used to specify which files should be selected from the file system. For more information on glob pattern matching look <a href=\"https://en.wikipedia.org/wiki/Glob_(programming)\">here</a>.",
37
37
"type": "array",
38
38
"items": {
39
39
"type": "string"
@@ -53,8 +53,8 @@
53
53
"primary_key": {
54
54
"title": "Primary Key",
55
55
"description": "The column or columns (for a composite key) that serves as the unique identifier of a record. If empty, the primary key will default to the parser's default primary key.",
56
-
"type": "string",
57
-
"airbyte_hidden": true
56
+
"airbyte_hidden": true,
57
+
"type": "string"
58
58
},
59
59
"days_to_sync_if_history_is_full": {
60
60
"title": "Days To Sync If History Is Full",
@@ -229,6 +229,12 @@
229
229
"type": "string"
230
230
},
231
231
"uniqueItems": true
232
+
},
233
+
"ignore_errors_on_fields_mismatch": {
234
+
"title": "Ignore errors on field mismatch",
235
+
"description": "Whether to ignore errors that occur when the number of fields in the CSV does not match the number of columns in the schema.",
236
+
"default": false,
237
+
"type": "boolean"
232
238
}
233
239
},
234
240
"required": ["filetype"]
@@ -276,20 +282,20 @@
276
282
"type": "string"
277
283
},
278
284
"skip_unprocessable_files": {
279
-
"type": "boolean",
280
-
"default": true,
281
285
"title": "Skip Unprocessable Files",
282
286
"description": "If true, skip files that cannot be parsed and pass the error message along as the _ab_source_file_parse_error field. If false, fail the sync.",
283
-
"always_show": true
287
+
"default": true,
288
+
"always_show": true,
289
+
"type": "boolean"
284
290
},
285
291
"strategy": {
286
-
"type": "string",
292
+
"title": "Parsing Strategy",
293
+
"description": "The strategy used to parse documents. `fast` extracts text directly from the document which doesn't work for all files. `ocr_only` is more reliable, but slower. `hi_res` is the most reliable, but requires an API key and a hosted instance of unstructured and can't be used with local mode. See the unstructured.io documentation for more details: https://unstructured-io.github.io/unstructured/core/partition.html#partition-pdf",
294
+
"default": "auto",
287
295
"always_show": true,
288
296
"order": 0,
289
-
"default": "auto",
290
-
"title": "Parsing Strategy",
291
297
"enum": ["auto", "fast", "ocr_only", "hi_res"],
292
-
"description": "The strategy used to parse documents. `fast` extracts text directly from the document which doesn't work for all files. `ocr_only` is more reliable, but slower. `hi_res` is the most reliable, but requires an API key and a hosted instance of unstructured and can't be used with local mode. See the unstructured.io documentation for more details: https://unstructured-io.github.io/unstructured/core/partition.html#partition-pdf"
0 commit comments