Skip to content

Commit 296432e

Browse files
authored
source-yandex-metrica: ensure inline schemas, updated cdk, poetry (where possible) (#37296)
1 parent 990e0c1 commit 296432e

File tree

9 files changed

+1347
-137
lines changed

9 files changed

+1347
-137
lines changed

airbyte-integrations/connectors/source-yandex-metrica/Dockerfile

-38
This file was deleted.
Original file line numberDiff line numberDiff line change
@@ -1,69 +1,55 @@
1-
# Yandex Metrica Source
1+
# Yandex-Metrica source connector
22

3-
This is the repository for the Yandex Metrica 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/yandex-metrica).
3+
4+
This is the repository for the Yandex-Metrica source connector, written in Python.
5+
For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/yandex-metrica).
56

67
## Local development
78

89
### Prerequisites
9-
**To iterate on this connector, make sure to complete this prerequisites section.**
10-
11-
#### Minimum Python version required `= 3.9.0`
10+
* Python (~=3.9)
11+
* Poetry (~=1.7) - installation instructions [here](https://python-poetry.org/docs/#installation)
1212

13-
#### Build & Activate Virtual Environment and install dependencies
14-
From this connector directory, create a virtual environment:
15-
```
16-
python -m venv .venv
17-
```
1813

19-
This will generate a virtualenv for this module in `.venv/`. Make sure this venv is active in your
20-
development environment of choice. To activate it from the terminal, run:
21-
```
22-
source .venv/bin/activate
23-
pip install -r requirements.txt
24-
pip install '.[tests]'
14+
### Installing the connector
15+
From this connector directory, run:
16+
```bash
17+
poetry install --with dev
2518
```
26-
If you are in an IDE, follow your IDE's instructions to activate the virtualenv.
2719

28-
Note that while we are installing dependencies from `requirements.txt`, you should only edit `setup.py` for your dependencies. `requirements.txt` is
29-
used for editable installs (`pip install -e`) to pull in Python dependencies from the monorepo and will call `setup.py`.
30-
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
31-
should work as you expect.
3220

33-
#### Create credentials
34-
**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/yandex-metrica)
21+
### Create credentials
22+
**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.com/integrations/sources/yandex-metrica)
3523
to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_yandex_metrica/spec.yaml` file.
3624
Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
37-
See `integration_tests/sample_config.json` for a sample config file.
25+
See `sample_files/sample_config.json` for a sample config file.
3826

39-
**If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source yandex-metrica test creds`
40-
and place them into `secrets/config.json`.
4127

4228
### Locally running the connector
4329
```
44-
python main.py spec
45-
python main.py check --config secrets/config.json
46-
python main.py discover --config secrets/config.json
47-
python main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.json
30+
poetry run source-yandex-metrica spec
31+
poetry run source-yandex-metrica check --config secrets/config.json
32+
poetry run source-yandex-metrica discover --config secrets/config.json
33+
poetry run source-yandex-metrica read --config secrets/config.json --catalog sample_files/configured_catalog.json
4834
```
4935

50-
### Locally running the connector docker image
51-
36+
### Running unit tests
37+
To run unit tests locally, from the connector directory run:
38+
```
39+
poetry run pytest unit_tests
40+
```
5241

53-
#### Build
54-
**Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**
42+
### Building the docker image
43+
1. Install [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md)
44+
2. Run the following command to build the docker image:
5545
```bash
5646
airbyte-ci connectors --name=source-yandex-metrica build
5747
```
5848

59-
An image will be built with the tag `airbyte/source-yandex-metrica:dev`.
49+
An image will be available on your host with the tag `airbyte/source-yandex-metrica:dev`.
6050

61-
**Via `docker build`:**
62-
```bash
63-
docker build -t airbyte/source-yandex-metrica:dev .
64-
```
6551

66-
#### Run
52+
### Running as a docker container
6753
Then run any of the connector commands as follows:
6854
```
6955
docker run --rm airbyte/source-yandex-metrica:dev spec
@@ -72,29 +58,34 @@ docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-yandex-metrica:dev dis
7258
docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-yandex-metrica:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
7359
```
7460

75-
## Testing
61+
### Running our CI test suite
7662
You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
7763
```bash
7864
airbyte-ci connectors --name=source-yandex-metrica test
7965
```
8066

8167
### Customizing acceptance Tests
82-
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.
68+
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.
8369
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.
8470

85-
## Dependency Management
86-
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.
87-
We split dependencies between two groups, dependencies that are:
88-
* required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
89-
* required for the testing need to go to `TEST_REQUIREMENTS` list
71+
### Dependency Management
72+
All of your dependencies should be managed via Poetry.
73+
To add a new dependency, run:
74+
```bash
75+
poetry add <package-name>
76+
```
77+
78+
Please commit the changes to `pyproject.toml` and `poetry.lock` files.
9079

91-
### Publishing a new version of the connector
80+
## Publishing a new version of the connector
9281
You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
9382
1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-yandex-metrica test`
94-
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).
83+
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+
- bump the `dockerImageTag` value in in `metadata.yaml`
85+
- bump the `version` value in `pyproject.toml`
9586
3. Make sure the `metadata.yaml` content is up to date.
96-
4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/yandex-metrica.md`).
87+
4. Make sure the connector documentation and its changelog is up to date (`docs/integrations/sources/yandex-metrica.md`).
9788
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).
9889
6. Pat yourself on the back for being an awesome contributor.
9990
7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
100-
91+
8. Once your PR is merged, the new version of the connector will be automatically published to Docker Hub and our connector registry.

airbyte-integrations/connectors/source-yandex-metrica/metadata.yaml

+7-5
Original file line numberDiff line numberDiff line change
@@ -5,26 +5,28 @@ data:
55
allowedHosts:
66
hosts:
77
- api-metrica.yandex.net
8+
connectorBuildOptions:
9+
baseImage: docker.io/airbyte/python-connector-base:1.2.0@sha256:c22a9d97464b69d6ef01898edf3f8612dc11614f05a84984451dde195f337db9
810
connectorSubtype: api
911
connectorType: source
1012
definitionId: 7865dce4-2211-4f6a-88e5-9d0fe161afe7
11-
dockerImageTag: 1.0.0
13+
dockerImageTag: 1.0.4
1214
dockerRepository: airbyte/source-yandex-metrica
1315
documentationUrl: https://docs.airbyte.com/integrations/sources/yandex-metrica
1416
githubIssueLabel: source-yandex-metrica
1517
icon: yandexmetrica.svg
1618
license: MIT
1719
name: Yandex Metrica
18-
remoteRegistries:
19-
pypi:
20-
enabled: true
21-
packageName: airbyte-source-yandex-metrica
2220
registries:
2321
cloud:
2422
enabled: true
2523
oss:
2624
enabled: true
2725
releaseStage: beta
26+
remoteRegistries:
27+
pypi:
28+
enabled: true
29+
packageName: airbyte-source-yandex-metrica
2830
supportLevel: community
2931
tags:
3032
- language:python

0 commit comments

Comments
 (0)