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/xero)
23
-
to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_xero/spec.yaml` file.
27
+
to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `spec` inside `manifest.yaml` file.
24
28
Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
25
-
See `sample_files/sample_config.json` for a sample config file.
29
+
See `integration_tests/sample_config.json` for a sample config file.
26
30
27
31
28
32
### Locally running the connector
33
+
34
+
29
35
```
30
36
poetry run source-xero spec
31
37
poetry run source-xero check --config secrets/config.json
32
38
poetry run source-xero discover --config secrets/config.json
33
-
poetry run source-xero read --config secrets/config.json --catalog sample_files/configured_catalog.json
39
+
poetry run source-xero read --config secrets/config.json --catalog integration_tests/configured_catalog.json
34
40
```
35
41
36
-
### Running unit tests
37
-
To run unit tests locally, from the connector directory run:
42
+
### Running tests
43
+
44
+
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):
63
75
```bash
64
76
airbyte-ci connectors --name=source-xero test
65
77
```
66
78
67
79
### Customizing acceptance Tests
80
+
68
81
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.
69
82
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.
70
83
71
84
### Dependency Management
85
+
72
86
All of your dependencies should be managed via Poetry.
73
87
To add a new dependency, run:
74
88
```bash
@@ -78,14 +92,20 @@ poetry add <package-name>
78
92
Please commit the changes to `pyproject.toml` and `poetry.lock` files.
79
93
80
94
## Publishing a new version of the connector
95
+
81
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?
82
97
1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-xero test`
98
+
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)):
99
+
- bump the `dockerImageTag` value in in `metadata.yaml`
100
+
- bump the `version` value in `pyproject.toml`
83
101
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
102
- bump the `dockerImageTag` value in in `metadata.yaml`
85
103
- bump the `version` value in `pyproject.toml`
86
104
3. Make sure the `metadata.yaml` content is up to date.
87
105
4. Make sure the connector documentation and its changelog is up to date (`docs/integrations/sources/xero.md`).
106
+
4. Make sure the connector documentation and its changelog is up to date (`docs/integrations/sources/xero.md`).
88
107
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).
89
108
6. Pat yourself on the back for being an awesome contributor.
90
109
7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
110
+
8. Once your PR is merged, the new version of the connector will be automatically published to Docker Hub and our connector registry.
91
111
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-xero/metadata.yaml
+25-14
Original file line number
Diff line number
Diff line change
@@ -2,33 +2,46 @@ data:
2
2
allowedHosts:
3
3
hosts:
4
4
- api.xero.com
5
+
registries:
6
+
oss:
7
+
enabled: true
8
+
cloud:
9
+
enabled: false
10
+
remoteRegistries:
11
+
pypi:
12
+
enabled: true
13
+
packageName: airbyte-source-xero
14
+
releases:
15
+
breakingChanges:
16
+
1.0.0:
17
+
upgradeDeadline: "2024-06-30"
18
+
message:
19
+
The source Xero connector is being migrated from the Python CDK to our declarative low-code CDK. The authorization method was changed from OAuth 2.0 to Access Token. Due to changes in authorization, users will need to generate an access token within source Xero and reset source configuration. For more information, see our migration documentation for source Xero.
20
+
Important - The authentication scheme is using access_token instead of Oauth 2.0 from this version.
21
+
connectorBuildOptions:
22
+
# Please update to the latest version of the connector base image.
0 commit comments