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
A collection of tools and checks run by Github Actions
3
+
A collection of utilities for working with Airbyte connectors.
4
4
5
-
## Running Locally
5
+
#Setup
6
6
7
-
From this directory, create a virtual environment:
7
+
## Prerequisites
8
8
9
-
```
10
-
python3 -m venv .venv
9
+
#### Poetry
10
+
11
+
Before you can start working on this project, you will need to have Poetry installed on your system. Please follow the instructions below to install Poetry:
12
+
13
+
1. Open your terminal or command prompt.
14
+
2. Install Poetry using the recommended installation method:
This will generate a virtualenv for this module in `.venv/`. Make sure this venv is active in your
14
-
development environment of choice. To activate it from the terminal, run:
20
+
Alternatively, you can use `pip` to install Poetry:
15
21
16
22
```bash
17
-
source .venv/bin/activate
18
-
pip install -e .# assuming you are in the ./airbyte-ci/connectors/connector_ops directory
23
+
pip install --user poetry
19
24
```
20
25
21
-
pip will make binaries for all the commands in setup.py, so you can run `allowed-hosts-checks` directly from the virtual-env
26
+
3. After the installation is complete, close and reopen your terminal to ensure the newly installed `poetry` command is available in your system's PATH.
22
27
23
-
## Testing Locally
28
+
For more detailed instructions and alternative installation methods, please refer to the official Poetry documentation: https://python-poetry.org/docs/#installation
24
29
25
-
To install requirements to run unit tests, use:
30
+
### Using Poetry in the Project
26
31
27
-
```
28
-
pip install -e ".[tests]"
29
-
```
32
+
Once Poetry is installed, you can use it to manage the project's dependencies and virtual environment. To get started, navigate to the project's root directory in your terminal and follow these steps:
30
33
31
-
Unit tests are currently configured to be run from the base `airbyte` directory. You can run the tests from that directory with the following command:
Copy file name to clipboardExpand all lines: airbyte-ci/connectors/pipelines/README.md
+2
Original file line number
Diff line number
Diff line change
@@ -122,6 +122,7 @@ Available commands:
122
122
|`--use-remote-secrets`| False | True | If True, connectors configuration will be pulled from Google Secret Manager. Requires the GCP_GSM_CREDENTIALS environment variable to be set with a service account with permission to read GSM secrets. If False the connector configuration will be read from the local connector `secrets` folder. |
123
123
|`--name`| True || Select a specific connector for which the pipeline will run. Can be used multiple time to select multiple connectors. The expected name is the connector technical name. e.g. `source-pokeapi`|
124
124
|`--support-level`| True || Select connectors with a specific support level: `community`, `certified`. Can be used multiple times to select multiple support levels. |
125
+
|`--metadata-query`| False || Filter connectors by the `data` field in the metadata file using a [simpleeval](https://github.com/danthedeckie/simpleeval) query. e.g. 'data.ab_internal.ql == 200' |
125
126
|`--language`| True || Select connectors with a specific language: `python`, `low-code`, `java`. Can be used multiple times to select multiple languages. |
126
127
|`--modified`| False | False | Run the pipeline on only the modified connectors on the branch or previous commit (depends on the pipeline implementation). |
127
128
|`--concurrency`| False | 5 | Control the number of connector pipelines that can run in parallel. Useful to speed up pipelines or control their resource usage. |
@@ -405,6 +406,7 @@ This command runs the Python tests for a airbyte-ci poetry package.
0 commit comments