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/exchange-rates)
11
-
to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_exchange_rates/spec.yaml` file.
26
+
to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `spec` inside `src/source_exchange_rates/mnifest.yaml` file.
12
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.
13
28
See `integration_tests/sample_config.json` for a sample config file.
14
29
15
-
**If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source exchange-rates test creds`
16
-
and place them into `secrets/config.json`.
17
30
18
-
### Locally running the connector docker image
31
+
### Locally running the connector
19
32
20
-
#### Build
33
+
```
34
+
poetry run source-exchange-rates spec
35
+
poetry run source-exchange-rates check --config secrets/config.json
36
+
poetry run source-exchange-rates discover --config secrets/config.json
37
+
poetry run source-exchange-rates 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):
50
-
51
72
```bash
52
73
airbyte-ci connectors --name=source-exchange-rates test
53
74
```
54
75
55
76
### Customizing acceptance Tests
56
77
57
-
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.
78
+
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.
58
79
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.
59
80
60
-
## Dependency Management
81
+
###Dependency Management
61
82
62
-
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.
63
-
We split dependencies between two groups, dependencies that are:
83
+
All of your dependencies should be managed via Poetry.
84
+
To add a new dependency, run:
85
+
```bash
86
+
poetry add <package-name>
87
+
```
64
88
65
-
- required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
66
-
- required for the testing need to go to `TEST_REQUIREMENTS` list
89
+
Please commit the changes to `pyproject.toml` and `poetry.lock` files.
67
90
68
-
###Publishing a new version of the connector
91
+
## Publishing a new version of the connector
69
92
70
93
You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
71
-
72
94
1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-exchange-rates test`
73
-
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).
95
+
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)):
96
+
- bump the `dockerImageTag` value in in `metadata.yaml`
97
+
- bump the `version` value in `pyproject.toml`
74
98
3. Make sure the `metadata.yaml` content is up to date.
75
-
4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/exchange-rates.md`).
99
+
4. Make sure the connector documentation and its changelog is up to date (`docs/integrations/sources/exchange-rates.md`).
76
100
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).
77
101
6. Pat yourself on the back for being an awesome contributor.
78
102
7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
103
+
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