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
**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.com/integrations/sources/outreach)
24
-
to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_outreach/spec.yaml` file.
26
+
to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `spec` inside `manifest.yaml` file.
25
27
Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
26
28
See `sample_files/sample_config.json` for a sample config file.
27
29
30
+
28
31
### Locally running the connector
29
32
33
+
30
34
```
31
35
poetry run source-outreach spec
32
36
poetry run source-outreach check --config secrets/config.json
33
37
poetry run source-outreach discover --config secrets/config.json
34
38
poetry run source-outreach read --config secrets/config.json --catalog sample_files/configured_catalog.json
39
+
poetry run source-outreach spec
40
+
poetry run source-outreach check --config secrets/config.json
41
+
poetry run source-outreach discover --config secrets/config.json
42
+
poetry run source-outreach read --config secrets/config.json --catalog sample_files/configured_catalog.json
35
43
```
36
44
37
-
### Running unit tests
45
+
### Running tests
38
46
39
-
To run unit tests locally, from the connector directory run:
47
+
To run 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):
70
81
71
82
```bash
@@ -74,14 +85,15 @@ airbyte-ci connectors --name=source-outreach test
74
85
75
86
### Customizing acceptance Tests
76
87
88
+
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.
89
+
77
90
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.
78
91
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.
79
92
80
93
### Dependency Management
81
94
82
-
All of your dependencies should be managed via Poetry.
95
+
All of your dependencies should be managed via Poetry.
83
96
To add a new dependency, run:
84
-
85
97
```bash
86
98
poetry add <package-name>
87
99
```
@@ -93,12 +105,13 @@ Please commit the changes to `pyproject.toml` and `poetry.lock` files.
93
105
You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
94
106
95
107
1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-outreach test`
96
-
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)):
97
-
- bump the `dockerImageTag` value in in `metadata.yaml`
98
-
- bump the `version` value in `pyproject.toml`
108
+
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)):
109
+
- bump the `dockerImageTag` value in in `metadata.yaml`
110
+
- bump the `version` value in `pyproject.toml`
99
111
3. Make sure the `metadata.yaml` content is up to date.
100
112
4. Make sure the connector documentation and its changelog is up to date (`docs/integrations/sources/outreach.md`).
113
+
4. Make sure the connector documentation and its changelog is up to date (`docs/integrations/sources/outreach.md`).
101
114
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
115
6. Pat yourself on the back for being an awesome contributor.
103
116
7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
104
-
8. Once your PR is merged, the new version of the connector will be automatically published to Docker Hub and our connector registry.
117
+
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