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
This is the repository for the Pivotal Tracker source connector, written in Python.
4
-
For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/pivotal-tracker).
3
+
This is the repository for the Pivotal Tracker configuration based source connector.
4
+
For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/pivotal-tracker).
5
5
6
6
## Local development
7
7
8
8
### Prerequisites
9
9
10
-
**To iterate on this connector, make sure to complete this prerequisites section.**
#### Build & Activate Virtual Environment and install dependencies
15
14
16
-
From this connector directory, create a virtual environment:
15
+
### Installing the connector
17
16
18
-
```
19
-
python -m venv .venv
20
-
```
21
-
22
-
This will generate a virtualenv for this module in `.venv/`. Make sure this venv is active in your
23
-
development environment of choice. To activate it from the terminal, run:
24
-
25
-
```
26
-
source .venv/bin/activate
27
-
pip install -r requirements.txt
28
-
pip install '.[tests]'
17
+
From this connector directory, run:
18
+
```bash
19
+
poetry install --with dev
29
20
```
30
21
31
-
If you are in an IDE, follow your IDE's instructions to activate the virtualenv.
32
22
33
-
Note that while we are installing dependencies from `requirements.txt`, you should only edit `setup.py` for your dependencies. `requirements.txt` is
34
-
used for editable installs (`pip install -e`) to pull in Python dependencies from the monorepo and will call `setup.py`.
35
-
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
36
-
should work as you expect.
23
+
### Create credentials
37
24
38
-
#### Create credentials
39
-
40
-
**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/pivotal-tracker)
41
-
to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_pivotal_tracker/spec.json` file.
25
+
**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.com/integrations/sources/pivotal-tracker)
26
+
to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `spec` inside `manifest.yaml` file.
42
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.
43
28
See `integration_tests/sample_config.json` for a sample config file.
44
29
45
-
**If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source pivotal-tracker 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):
89
74
@@ -93,25 +78,30 @@ airbyte-ci connectors --name=source-pivotal-tracker test
93
78
94
79
### Customizing acceptance Tests
95
80
96
-
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.
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.
97
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.
98
83
99
-
## Dependency Management
84
+
###Dependency Management
100
85
101
-
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.
102
-
We split dependencies between two groups, dependencies that are:
86
+
All of your dependencies should be managed via Poetry.
87
+
To add a new dependency, run:
88
+
```bash
89
+
poetry add <package-name>
90
+
```
103
91
104
-
- required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
105
-
- required for the testing need to go to `TEST_REQUIREMENTS` list
92
+
Please commit the changes to `pyproject.toml` and `poetry.lock` files.
106
93
107
-
###Publishing a new version of the connector
94
+
## Publishing a new version of the connector
108
95
109
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?
110
97
111
98
1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-pivotal-tracker test`
112
-
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).
99
+
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)):
100
+
- bump the `dockerImageTag` value in in `metadata.yaml`
101
+
- bump the `version` value in `pyproject.toml`
113
102
3. Make sure the `metadata.yaml` content is up to date.
114
-
4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/pivotal-tracker.md`).
103
+
4. Make sure the connector documentation and its changelog is up to date (`docs/integrations/sources/pivotal-tracker.md`).
115
104
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).
116
105
6. Pat yourself on the back for being an awesome contributor.
117
106
7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
107
+
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