| Name | airbyte-source-dv-360 JSON |
| Version |
0.1.0
JSON |
| download |
| home_page | |
| Summary | Source implementation for Display & Video 360. |
| upload_time | 2024-01-30 17:38:20 |
| maintainer | |
| docs_url | None |
| author | Airbyte |
| requires_python | |
| license | |
| keywords |
|
| VCS |
|
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# DISPLAY & VIDEO 360 Source
This is the repository for the DISPLAY & VIDEO 360 source connector, written in Python.
For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/dv360).
**To iterate on this connector, make sure to complete this prerequisites section.**
From this connector directory, create a virtual environment:
```
python -m venv .venv
```
This will generate a virtualenv for this module in `.venv/`. Make sure this venv is active in your
development environment of choice. To activate it from the terminal, run:
```
source .venv/bin/activate
pip install -r requirements.txt
```
If you are in an IDE, follow your IDE's instructions to activate the virtualenv.
Note that while we are installing dependencies from `requirements.txt`, you should only edit `setup.py` for your dependencies. `requirements.txt` is
used for editable installs (`pip install -e`) to pull in Python dependencies from the monorepo and will call `setup.py`.
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
should work as you expect.
**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/dv360)
to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_dv_360/spec.json` file.
Note that the `secrets` directory is gitignored by default, so there is no danger of accidentally checking in sensitive information.
See `integration_tests/sample_config.json` for a sample config file.
**If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source dv360 test creds`
and place them into `secrets/config.json`.
```
python main.py spec
python main.py check --config secrets/config.json
python main.py discover --config secrets/config.json
python main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.json
```
**Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**
```bash
airbyte-ci connectors --name=source-dv-360 build
```
An image will be built with the tag `airbyte/source-dv-360:dev`.
**Via `docker build`:**
```bash
docker build -t airbyte/source-dv-360:dev .
```
Then run any of the connector commands as follows:
```
docker run --rm airbyte/source-dv-360:dev spec
docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-dv-360:dev check --config /secrets/config.json
docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-dv-360:dev discover --config /secrets/config.json
docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-dv-360:dev 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):
```bash
airbyte-ci connectors --name=source-dv-360 test
```
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.
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.
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.
We split dependencies between two groups, dependencies that are:
* required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
* required for the testing need to go to `TEST_REQUIREMENTS` list
You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-dv-360 test`
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).
3. Make sure the `metadata.yaml` content is up to date.
4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/dv-360.md`).
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).
6. Pat yourself on the back for being an awesome contributor.
7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
Raw data
{
"_id": null,
"home_page": "",
"name": "airbyte-source-dv-360",
"maintainer": "",
"docs_url": null,
"requires_python": "",
"maintainer_email": "",
"keywords": "",
"author": "Airbyte",
"author_email": "contact@airbyte.io",
"download_url": "https://files.pythonhosted.org/packages/fa/3e/db82027b245159e38725be63e0d8b97bdbbaee8a3ce2c0dc5876467a590f/airbyte-source-dv-360-0.1.0.tar.gz",
"platform": null,
"description": "# DISPLAY & VIDEO 360 Source\n\nThis is the repository for the DISPLAY & VIDEO 360 source connector, written in Python.\nFor information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/dv360).\n\n\n**To iterate on this connector, make sure to complete this prerequisites section.**\n\n\nFrom this connector directory, create a virtual environment:\n```\npython -m venv .venv\n```\n\nThis will generate a virtualenv for this module in `.venv/`. Make sure this venv is active in your\ndevelopment environment of choice. To activate it from the terminal, run:\n```\nsource .venv/bin/activate\npip install -r requirements.txt\n```\nIf you are in an IDE, follow your IDE's instructions to activate the virtualenv.\n\nNote that while we are installing dependencies from `requirements.txt`, you should only edit `setup.py` for your dependencies. `requirements.txt` is\nused for editable installs (`pip install -e`) to pull in Python dependencies from the monorepo and will call `setup.py`.\nIf 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\nshould work as you expect.\n\n**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/dv360)\nto generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_dv_360/spec.json` file.\nNote that the `secrets` directory is gitignored by default, so there is no danger of accidentally checking in sensitive information.\nSee `integration_tests/sample_config.json` for a sample config file.\n\n**If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source dv360 test creds`\nand place them into `secrets/config.json`.\n\n```\npython main.py spec\npython main.py check --config secrets/config.json\npython main.py discover --config secrets/config.json\npython main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.json\n```\n\n\n\n**Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**\n```bash\nairbyte-ci connectors --name=source-dv-360 build\n```\n\nAn image will be built with the tag `airbyte/source-dv-360:dev`.\n\n**Via `docker build`:**\n```bash\ndocker build -t airbyte/source-dv-360:dev .\n```\n\nThen run any of the connector commands as follows:\n```\ndocker run --rm airbyte/source-dv-360:dev spec\ndocker run --rm -v $(pwd)/secrets:/secrets airbyte/source-dv-360:dev check --config /secrets/config.json\ndocker run --rm -v $(pwd)/secrets:/secrets airbyte/source-dv-360:dev discover --config /secrets/config.json\ndocker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-dv-360:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json\n```\n\nYou can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):\n```bash\nairbyte-ci connectors --name=source-dv-360 test\n```\n\nCustomize `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.\nIf 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.\n\nAll 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.\nWe split dependencies between two groups, dependencies that are:\n* required for your connector to work need to go to `MAIN_REQUIREMENTS` list.\n* required for the testing need to go to `TEST_REQUIREMENTS` list\n\nYou've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?\n1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-dv-360 test`\n2. 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).\n3. Make sure the `metadata.yaml` content is up to date.\n4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/dv-360.md`).\n5. Create a Pull Request: use [our PR naming conventions](https://docs.airbyte.com/contributing-to-airbyte/resources/pull-requests-handbook/#pull-request-title-convention).\n6. Pat yourself on the back for being an awesome contributor.\n7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.\n",
"bugtrack_url": null,
"license": "",
"summary": "Source implementation for Display & Video 360.",
"version": "0.1.0",
"project_urls": null,
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "776c9275599ab7918555771beec94f6e94398ece3ac7f77831b166df4d88f40d",
"md5": "7a4de4a830075c07df83a8a6c441ac1c",
"sha256": "a0706befd1e3f9ca1e5ec7534ada2af0eb24c7dd50350d79a2289bf3f770d025"
},
"downloads": -1,
"filename": "airbyte_source_dv_360-0.1.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "7a4de4a830075c07df83a8a6c441ac1c",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": null,
"size": 31226,
"upload_time": "2024-01-30T17:38:18",
"upload_time_iso_8601": "2024-01-30T17:38:18.525611Z",
"url": "https://files.pythonhosted.org/packages/77/6c/9275599ab7918555771beec94f6e94398ece3ac7f77831b166df4d88f40d/airbyte_source_dv_360-0.1.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "fa3edb82027b245159e38725be63e0d8b97bdbbaee8a3ce2c0dc5876467a590f",
"md5": "ae4849746efa66141cfae4260f9ff92d",
"sha256": "f4668d3992ad422735509adc75a80707f939d810d15552fbfe4683d74abbfe55"
},
"downloads": -1,
"filename": "airbyte-source-dv-360-0.1.0.tar.gz",
"has_sig": false,
"md5_digest": "ae4849746efa66141cfae4260f9ff92d",
"packagetype": "sdist",
"python_version": "source",
"requires_python": null,
"size": 28910,
"upload_time": "2024-01-30T17:38:20",
"upload_time_iso_8601": "2024-01-30T17:38:20.127578Z",
"url": "https://files.pythonhosted.org/packages/fa/3e/db82027b245159e38725be63e0d8b97bdbbaee8a3ce2c0dc5876467a590f/airbyte-source-dv-360-0.1.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-01-30 17:38:20",
"github": false,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"lcname": "airbyte-source-dv-360"
}
