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
Follow the steps in the given link [Here](https://developers.zenefits.com/docs/sync-with-zenefits-button), This will generate and Bearer token for the user which can be used to interact with the API using the source-zenefits connector.
5
3
4
+
This is the repository for the Zenefits source connector, written in Python.
5
+
For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/zenefits).
This is the repository for the Zenefits configuration based source connector.
11
-
For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/zenefits).
12
13
13
-
## Local development
14
+
### Installing the connector
15
+
From this connector directory, run:
16
+
```bash
17
+
poetry install --with dev
18
+
```
19
+
14
20
15
-
####Create credentials
21
+
### Create credentials
16
22
**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.com/integrations/sources/zenefits)
17
23
to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_zenefits/spec.yaml` file.
18
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.
19
-
See `integration_tests/sample_config.json` for a sample config file.
25
+
See `sample_files/sample_config.json` for a sample config file.
20
26
21
-
**If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source zenefits test creds`
22
-
and place them into `secrets/config.json`.
23
27
24
-
### Locally running the connector docker image
28
+
### Locally running the connector
29
+
```
30
+
poetry run source-zenefits spec
31
+
poetry run source-zenefits check --config secrets/config.json
32
+
poetry run source-zenefits discover --config secrets/config.json
33
+
poetry run source-zenefits read --config secrets/config.json --catalog sample_files/configured_catalog.json
34
+
```
25
35
36
+
### Running unit tests
37
+
To run unit tests locally, from the connector directory run:
You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
51
63
```bash
52
64
airbyte-ci connectors --name=source-zenefits test
53
65
```
54
66
55
67
### Customizing acceptance Tests
56
-
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.
57
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.
58
70
59
-
## Dependency Management
60
-
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.
61
-
We split dependencies between two groups, dependencies that are:
62
-
* required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
63
-
* 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
+
```
64
77
65
-
### Publishing a new version of the connector
78
+
Please commit the changes to `pyproject.toml` and `poetry.lock` files.
79
+
80
+
## Publishing a new version of the connector
66
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?
67
82
1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-zenefits test`
68
-
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`
69
86
3. Make sure the `metadata.yaml` content is up to date.
70
-
4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/zenefits.md`).
87
+
4. Make sure the connector documentation and its changelog is up to date (`docs/integrations/sources/zenefits.md`).
71
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).
72
89
6. Pat yourself on the back for being an awesome contributor.
73
90
7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
74
-
91
+
8. Once your PR is merged, the new version of the connector will be automatically published to Docker Hub and our connector registry.
0 commit comments