airbyte-source-zenloop 0.1.42__tar.gz → 0.1.44__tar.gz

airbyte_source_zenloop-0.1.44/.airbyte-pypi-readme.md

@@ -0,0 +1,7 @@
+# Zenloop
+
+This package contains the Airbyte Zenloop connector.
+
+Airbyte is open-source data movement for ELT pipelines and AI agents. It moves data from APIs, databases, and files to warehouses, lakes, and AI applications.
+
+Airbyte provides a catalog of 600+ connectors for APIs, databases, data warehouses, data lakes, and AI applications. Use this package with [PyAirbyte](https://docs.airbyte.com/developers/pyairbyte) to run the connector from Python.

airbyte_source_zenloop-0.1.44/PKG-INFO

@@ -0,0 +1,27 @@
+Metadata-Version: 2.1
+Name: airbyte-source-zenloop
+Version: 0.1.44
+Summary: Source implementation for Zenloop.
+Home-page: https://airbyte.com
+License: ELv2
+Author: Alexander Batoulis
+Author-email: alexander.batoulis@hometogo.com
+Requires-Python: >=3.9,<3.12
+Classifier: License :: Other/Proprietary License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Requires-Dist: airbyte-cdk (==0.80.0)
+Project-URL: Documentation, https://docs.airbyte.com/integrations/sources/zenloop
+Project-URL: Repository, https://github.com/airbytehq/airbyte
+Description-Content-Type: text/markdown
+
+# Zenloop
+
+This package contains the Airbyte Zenloop connector.
+
+Airbyte is open-source data movement for ELT pipelines and AI agents. It moves data from APIs, databases, and files to warehouses, lakes, and AI applications.
+
+Airbyte provides a catalog of 600+ connectors for APIs, databases, data warehouses, data lakes, and AI applications. Use this package with [PyAirbyte](https://docs.airbyte.com/developers/pyairbyte) to run the connector from Python.
+

{airbyte_source_zenloop-0.1.42 → airbyte_source_zenloop-0.1.44}/pyproject.toml

@@ -1,24 +1,19 @@
 [build-system]
-requires = [
-    "poetry-core>=1.0.0",
-]
+requires = [ "poetry-core>=1.0.0",]
 build-backend = "poetry.core.masonry.api"
 
 [tool.poetry]
-version = "0.1.42"
+version = "0.1.44"
 name = "airbyte-source-zenloop"
 description = "Source implementation for Zenloop."
-authors = [
-    "Airbyte <contact@airbyte.io>",
-]
-license = "MIT"
-readme = "README.md"
+authors = [ "Alexander Batoulis <alexander.batoulis@hometogo.com>",]
+license = "ELv2"
+readme = ".airbyte-pypi-readme.md"
 documentation = "https://docs.airbyte.com/integrations/sources/zenloop"
 homepage = "https://airbyte.com"
 repository = "https://github.com/airbytehq/airbyte"
-packages = [
-    { include = "source_zenloop" },
-]
+[[tool.poetry.packages]]
+include = "source_zenloop"
 
 [tool.poetry.dependencies]
 python = "^3.9,<3.12"
@@ -30,5 +25,13 @@ source-zenloop = "source_zenloop.run:run"
 [tool.poetry.group.dev.dependencies]
 pytest-mock = "^3.6.1"
 requests-mock = "^1.9.3"
-pytest = "^6.1"
+pytest = "^8.0.0"
 responses = "^0.13.3"
+
+
+[tool.poe]
+include = [
+    # Shared tasks definition file(s) can be imported here.
+    # Run `poe` or `poe --help` to see the list of available tasks.
+    "${POE_GIT_DIR}/poe-tasks/poetry-connector-tasks.toml",
+]

{airbyte_source_zenloop-0.1.42 → airbyte_source_zenloop-0.1.44}/source_zenloop/manifest.yaml

@@ -166,7 +166,7 @@ definitions:
     datetime_format: "%Y-%m-%dT%H:%M:%S.%fZ"
     cursor_granularity: "PT0.000001S"
     start_datetime:
-      datetime: "{{ config['date_from'] }}"
+      datetime: "{{ config['date_from'][:10] if config.get('date_from') else today_utc() }}"
       datetime_format: "%Y-%m-%d"
     end_datetime:
       datetime: "{{ today_utc() }}"

airbyte_source_zenloop-0.1.42/PKG-INFO

@@ -1,124 +0,0 @@
-Metadata-Version: 2.3
-Name: airbyte-source-zenloop
-Version: 0.1.42
-Summary: Source implementation for Zenloop.
-License: MIT
-Author: Airbyte
-Author-email: contact@airbyte.io
-Requires-Python: >=3.9,<3.12
-Classifier: License :: OSI Approved :: MIT License
-Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.9
-Classifier: Programming Language :: Python :: 3.10
-Classifier: Programming Language :: Python :: 3.11
-Requires-Dist: airbyte-cdk (==0.80.0)
-Project-URL: Documentation, https://docs.airbyte.com/integrations/sources/zenloop
-Project-URL: Homepage, https://airbyte.com
-Project-URL: Repository, https://github.com/airbytehq/airbyte
-Description-Content-Type: text/markdown
-
-# Zenloop source connector
-
-This is the repository for the Zenloop source connector, written in Python.
-For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/zenloop).
-
-## Local development
-
-### Prerequisites
-
-- Python (~=3.9)
-- Poetry (~=1.7) - installation instructions [here](https://python-poetry.org/docs/#installation)
-
-### Installing the connector
-
-From this connector directory, run:
-
-```bash
-poetry install --with dev
-```
-
-### Create credentials
-
-**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.com/integrations/sources/zenloop)
-to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_zenloop/spec.yaml` file.
-Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
-See `sample_files/sample_config.json` for a sample config file.
-
-### Locally running the connector
-
-```
-poetry run source-zenloop spec
-poetry run source-zenloop check --config secrets/config.json
-poetry run source-zenloop discover --config secrets/config.json
-poetry run source-zenloop read --config secrets/config.json --catalog sample_files/configured_catalog.json
-```
-
-### Running unit tests
-
-To run unit tests locally, from the connector directory run:
-
-```
-poetry run pytest unit_tests
-```
-
-### Building the docker image
-
-1. Install [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md)
-2. Run the following command to build the docker image:
-
-```bash
-airbyte-ci connectors --name=source-zenloop build
-```
-
-An image will be available on your host with the tag `airbyte/source-zenloop:dev`.
-
-### Running as a docker container
-
-Then run any of the connector commands as follows:
-
-```
-docker run --rm airbyte/source-zenloop:dev spec
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-zenloop:dev check --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-zenloop:dev discover --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-zenloop:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
-```
-
-### Running our CI test suite
-
-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-zenloop test
-```
-
-### Customizing acceptance Tests
-
-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.
-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.
-
-### Dependency Management
-
-All of your dependencies should be managed via Poetry.
-To add a new dependency, run:
-
-```bash
-poetry add <package-name>
-```
-
-Please commit the changes to `pyproject.toml` and `poetry.lock` files.
-
-## Publishing a new version of the connector
-
-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-zenloop test`
-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)):
-   - bump the `dockerImageTag` value in in `metadata.yaml`
-   - bump the `version` value in `pyproject.toml`
-3. Make sure the `metadata.yaml` content is up to date.
-4. Make sure the connector documentation and its changelog is up to date (`docs/integrations/sources/zenloop.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.
-8. Once your PR is merged, the new version of the connector will be automatically published to Docker Hub and our connector registry.
-

airbyte_source_zenloop-0.1.42/README.md

@@ -1,104 +0,0 @@
-# Zenloop source connector
-
-This is the repository for the Zenloop source connector, written in Python.
-For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/zenloop).
-
-## Local development
-
-### Prerequisites
-
-- Python (~=3.9)
-- Poetry (~=1.7) - installation instructions [here](https://python-poetry.org/docs/#installation)
-
-### Installing the connector
-
-From this connector directory, run:
-
-```bash
-poetry install --with dev
-```
-
-### Create credentials
-
-**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.com/integrations/sources/zenloop)
-to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_zenloop/spec.yaml` file.
-Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
-See `sample_files/sample_config.json` for a sample config file.
-
-### Locally running the connector
-
-```
-poetry run source-zenloop spec
-poetry run source-zenloop check --config secrets/config.json
-poetry run source-zenloop discover --config secrets/config.json
-poetry run source-zenloop read --config secrets/config.json --catalog sample_files/configured_catalog.json
-```
-
-### Running unit tests
-
-To run unit tests locally, from the connector directory run:
-
-```
-poetry run pytest unit_tests
-```
-
-### Building the docker image
-
-1. Install [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md)
-2. Run the following command to build the docker image:
-
-```bash
-airbyte-ci connectors --name=source-zenloop build
-```
-
-An image will be available on your host with the tag `airbyte/source-zenloop:dev`.
-
-### Running as a docker container
-
-Then run any of the connector commands as follows:
-
-```
-docker run --rm airbyte/source-zenloop:dev spec
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-zenloop:dev check --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-zenloop:dev discover --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-zenloop:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
-```
-
-### Running our CI test suite
-
-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-zenloop test
-```
-
-### Customizing acceptance Tests
-
-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.
-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.
-
-### Dependency Management
-
-All of your dependencies should be managed via Poetry.
-To add a new dependency, run:
-
-```bash
-poetry add <package-name>
-```
-
-Please commit the changes to `pyproject.toml` and `poetry.lock` files.
-
-## Publishing a new version of the connector
-
-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-zenloop test`
-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)):
-   - bump the `dockerImageTag` value in in `metadata.yaml`
-   - bump the `version` value in `pyproject.toml`
-3. Make sure the `metadata.yaml` content is up to date.
-4. Make sure the connector documentation and its changelog is up to date (`docs/integrations/sources/zenloop.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.
-8. Once your PR is merged, the new version of the connector will be automatically published to Docker Hub and our connector registry.