airbyte-source-microsoft-dataverse 0.1.2__tar.gz → 0.1.4__tar.gz

airbyte_source_microsoft_dataverse-0.1.4/PKG-INFO

@@ -0,0 +1,110 @@
+Metadata-Version: 2.1
+Name: airbyte-source-microsoft-dataverse
+Version: 0.1.4
+Summary: Source implementation for Microsoft Dataverse.
+Home-page: https://airbyte.com
+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/microsoft-dataverse
+Project-URL: Repository, https://github.com/airbytehq/airbyte
+Description-Content-Type: text/markdown
+
+# Microsoft-Dataverse source connector
+
+
+This is the repository for the Microsoft-Dataverse source connector, written in Python.
+For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/microsoft-dataverse).
+
+## 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/microsoft-dataverse)
+to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_microsoft_dataverse/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-microsoft-dataverse spec
+poetry run source-microsoft-dataverse check --config secrets/config.json
+poetry run source-microsoft-dataverse discover --config secrets/config.json
+poetry run source-microsoft-dataverse 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-microsoft-dataverse build
+```
+
+An image will be available on your host with the tag `airbyte/source-microsoft-dataverse:dev`.
+
+
+### Running as a docker container
+Then run any of the connector commands as follows:
+```
+docker run --rm airbyte/source-microsoft-dataverse:dev spec
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-microsoft-dataverse:dev check --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-microsoft-dataverse:dev discover --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-microsoft-dataverse: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-microsoft-dataverse 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-microsoft-dataverse 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/microsoft-dataverse.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_microsoft_dataverse-0.1.4/README.md

@@ -0,0 +1,91 @@
+# Microsoft-Dataverse source connector
+
+
+This is the repository for the Microsoft-Dataverse source connector, written in Python.
+For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.com/integrations/sources/microsoft-dataverse).
+
+## 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/microsoft-dataverse)
+to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_microsoft_dataverse/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-microsoft-dataverse spec
+poetry run source-microsoft-dataverse check --config secrets/config.json
+poetry run source-microsoft-dataverse discover --config secrets/config.json
+poetry run source-microsoft-dataverse 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-microsoft-dataverse build
+```
+
+An image will be available on your host with the tag `airbyte/source-microsoft-dataverse:dev`.
+
+
+### Running as a docker container
+Then run any of the connector commands as follows:
+```
+docker run --rm airbyte/source-microsoft-dataverse:dev spec
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-microsoft-dataverse:dev check --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-microsoft-dataverse:dev discover --config /secrets/config.json
+docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-microsoft-dataverse: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-microsoft-dataverse 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-microsoft-dataverse 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/microsoft-dataverse.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_microsoft_dataverse-0.1.4/pyproject.toml

@@ -0,0 +1,33 @@
+[build-system]
+requires = [
+    "poetry-core>=1.0.0",
+]
+build-backend = "poetry.core.masonry.api"
+
+[tool.poetry]
+version = "0.1.4"
+name = "airbyte-source-microsoft-dataverse"
+description = "Source implementation for Microsoft Dataverse."
+authors = [
+    "Airbyte <contact@airbyte.io>",
+]
+license = "MIT"
+readme = "README.md"
+documentation = "https://docs.airbyte.com/integrations/sources/microsoft-dataverse"
+homepage = "https://airbyte.com"
+repository = "https://github.com/airbytehq/airbyte"
+packages = [
+    { include = "source_microsoft_dataverse" },
+]
+
+[tool.poetry.dependencies]
+python = "^3.9,<3.12"
+airbyte-cdk = "0.80.0"
+
+[tool.poetry.scripts]
+source-microsoft-dataverse = "source_microsoft_dataverse.run:run"
+
+[tool.poetry.group.dev.dependencies]
+requests-mock = "^1.9.3"
+pytest = "^6.1"
+pytest-mock = "^3.6.1"

airbyte-source-microsoft-dataverse-0.1.2/PKG-INFO

@@ -1,99 +0,0 @@
-Metadata-Version: 2.1
-Name: airbyte-source-microsoft-dataverse
-Version: 0.1.2
-Summary: Source implementation for Microsoft Dataverse.
-Author: Airbyte
-Author-email: contact@airbyte.io
-Description-Content-Type: text/markdown
-Requires-Dist: airbyte-cdk~=0.2
-Provides-Extra: tests
-Requires-Dist: requests-mock~=1.9.3; extra == "tests"
-Requires-Dist: pytest~=6.1; extra == "tests"
-Requires-Dist: pytest-mock~=3.6.1; extra == "tests"
-
-# Microsoft Dataverse Source
-
-This is the repository for the Microsoft Dataverse source connector, written in Python.
-For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/microsoft-dataverse).
-
-
-**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
-pip install '.[tests]'
-```
-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/microsoft-dataverse)
-to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_microsoft_dataverse/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 `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 microsoft-dataverse 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-microsoft-dataverse build
-```
-
-An image will be built with the tag `airbyte/source-microsoft-dataverse:dev`.
-
-**Via `docker build`:**
-```bash
-docker build -t airbyte/source-microsoft-dataverse:dev .
-```
-
-Then run any of the connector commands as follows:
-```
-docker run --rm airbyte/source-microsoft-dataverse:dev spec
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-microsoft-dataverse:dev check --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-microsoft-dataverse:dev discover --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-microsoft-dataverse: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-microsoft-dataverse 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-microsoft-dataverse 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/microsoft-dataverse.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.

airbyte-source-microsoft-dataverse-0.1.2/README.md

@@ -1,100 +0,0 @@
-# Microsoft Dataverse Source
-
-This is the repository for the Microsoft Dataverse source connector, written in Python.
-For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/microsoft-dataverse).
-
-## Local development
-
-### Prerequisites
-**To iterate on this connector, make sure to complete this prerequisites section.**
-
-#### Minimum Python version required `= 3.9.0`
-
-#### Build & Activate Virtual Environment and install dependencies
-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
-pip install '.[tests]'
-```
-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.
-
-#### Create credentials
-**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/microsoft-dataverse)
-to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_microsoft_dataverse/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 `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 microsoft-dataverse test creds`
-and place them into `secrets/config.json`.
-
-### Locally running the connector
-```
-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
-```
-
-### Locally running the connector docker image
-
-
-#### Build
-**Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**
-```bash
-airbyte-ci connectors --name=source-microsoft-dataverse build
-```
-
-An image will be built with the tag `airbyte/source-microsoft-dataverse:dev`.
-
-**Via `docker build`:**
-```bash
-docker build -t airbyte/source-microsoft-dataverse:dev .
-```
-
-#### Run
-Then run any of the connector commands as follows:
-```
-docker run --rm airbyte/source-microsoft-dataverse:dev spec
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-microsoft-dataverse:dev check --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-microsoft-dataverse:dev discover --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-microsoft-dataverse:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
-```
-
-## Testing
-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-microsoft-dataverse test
-```
-
-### Customizing acceptance Tests
-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.
-
-## Dependency Management
-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
-
-### 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-microsoft-dataverse 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/microsoft-dataverse.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.
-

airbyte-source-microsoft-dataverse-0.1.2/airbyte_source_microsoft_dataverse.egg-info/PKG-INFO

@@ -1,99 +0,0 @@
-Metadata-Version: 2.1
-Name: airbyte-source-microsoft-dataverse
-Version: 0.1.2
-Summary: Source implementation for Microsoft Dataverse.
-Author: Airbyte
-Author-email: contact@airbyte.io
-Description-Content-Type: text/markdown
-Requires-Dist: airbyte-cdk~=0.2
-Provides-Extra: tests
-Requires-Dist: requests-mock~=1.9.3; extra == "tests"
-Requires-Dist: pytest~=6.1; extra == "tests"
-Requires-Dist: pytest-mock~=3.6.1; extra == "tests"
-
-# Microsoft Dataverse Source
-
-This is the repository for the Microsoft Dataverse source connector, written in Python.
-For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/microsoft-dataverse).
-
-
-**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
-pip install '.[tests]'
-```
-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/microsoft-dataverse)
-to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_microsoft_dataverse/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 `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 microsoft-dataverse 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-microsoft-dataverse build
-```
-
-An image will be built with the tag `airbyte/source-microsoft-dataverse:dev`.
-
-**Via `docker build`:**
-```bash
-docker build -t airbyte/source-microsoft-dataverse:dev .
-```
-
-Then run any of the connector commands as follows:
-```
-docker run --rm airbyte/source-microsoft-dataverse:dev spec
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-microsoft-dataverse:dev check --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-microsoft-dataverse:dev discover --config /secrets/config.json
-docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-microsoft-dataverse: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-microsoft-dataverse 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-microsoft-dataverse 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/microsoft-dataverse.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.

airbyte-source-microsoft-dataverse-0.1.2/airbyte_source_microsoft_dataverse.egg-info/SOURCES.txt

@@ -1,27 +0,0 @@
-README.md
-setup.cfg
-setup.py
-airbyte_source_microsoft_dataverse.egg-info/PKG-INFO
-airbyte_source_microsoft_dataverse.egg-info/SOURCES.txt
-airbyte_source_microsoft_dataverse.egg-info/dependency_links.txt
-airbyte_source_microsoft_dataverse.egg-info/entry_points.txt
-airbyte_source_microsoft_dataverse.egg-info/requires.txt
-airbyte_source_microsoft_dataverse.egg-info/top_level.txt
-integration_tests/__init__.py
-integration_tests/abnormal_state.json
-integration_tests/acceptance.py
-integration_tests/configured_catalog.json
-integration_tests/invalid_config.json
-integration_tests/sample_config.json
-integration_tests/sample_state.json
-source_microsoft_dataverse/__init__.py
-source_microsoft_dataverse/dataverse.py
-source_microsoft_dataverse/run.py
-source_microsoft_dataverse/source.py
-source_microsoft_dataverse/spec.yaml
-source_microsoft_dataverse/streams.py
-unit_tests/__init__.py
-unit_tests/test_dataverse.py
-unit_tests/test_incremental_streams.py
-unit_tests/test_source.py
-unit_tests/test_streams.py

airbyte-source-microsoft-dataverse-0.1.2/airbyte_source_microsoft_dataverse.egg-info/dependency_links.txt

@@ -1 +0,0 @@
-

airbyte-source-microsoft-dataverse-0.1.2/airbyte_source_microsoft_dataverse.egg-info/entry_points.txt

@@ -1,2 +0,0 @@
-[console_scripts]
-source-microsoft-dataverse = source_microsoft_dataverse.run:run

airbyte-source-microsoft-dataverse-0.1.2/airbyte_source_microsoft_dataverse.egg-info/requires.txt

@@ -1,6 +0,0 @@
-airbyte-cdk~=0.2
-
-[tests]
-requests-mock~=1.9.3
-pytest~=6.1
-pytest-mock~=3.6.1

airbyte-source-microsoft-dataverse-0.1.2/airbyte_source_microsoft_dataverse.egg-info/top_level.txt

@@ -1,3 +0,0 @@
-integration_tests
-source_microsoft_dataverse
-unit_tests

airbyte-source-microsoft-dataverse-0.1.2/integration_tests/__init__.py

@@ -1,3 +0,0 @@
-#
-# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
-#

airbyte-source-microsoft-dataverse-0.1.2/integration_tests/abnormal_state.json

@@ -1,5 +0,0 @@
-{
-  "<entity_name>": {
-    "$deltatoken": "12644418993!10/06/2050 20:06:12"
-  }
-}

airbyte-source-microsoft-dataverse-0.1.2/integration_tests/acceptance.py

@@ -1,16 +0,0 @@
-#
-# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
-#
-
-
-import pytest
-
-pytest_plugins = ("connector_acceptance_test.plugin",)
-
-
-@pytest.fixture(scope="session", autouse=True)
-def connector_setup():
-    """This fixture is a placeholder for external resources that acceptance test might require."""
-    # TODO: setup test dependencies if needed. otherwise remove the TODO comments
-    yield
-    # TODO: clean up test dependencies

airbyte-source-microsoft-dataverse-0.1.2/integration_tests/configured_catalog.json

@@ -1,15 +0,0 @@
-{
-  "streams": [
-    {
-      "stream": {
-        "name": "<entity_name>",
-        "json_schema": {},
-        "supported_sync_modes": ["full_refresh", "incremental"]
-      },
-      "cursor_field": ["modifiedon"],
-      "primary_key": [["<entity_primary_key>"]],
-      "sync_mode": "incremental",
-      "destination_sync_mode": "append"
-    }
-  ]
-}

airbyte-source-microsoft-dataverse-0.1.2/integration_tests/invalid_config.json

@@ -1,7 +0,0 @@
-{
-  "client_id": "<client_id>",
-  "tenant_id": "<tenant_id>",
-  "client_secret_value": "<invalid_client_secret>",
-  "url": "<url>",
-  "odata.maxpagesize": 100
-}

airbyte-source-microsoft-dataverse-0.1.2/integration_tests/sample_config.json

@@ -1,7 +0,0 @@
-{
-  "url": "<url>",
-  "client_id": "<client_id>",
-  "tenant_id": "<tenant_id>",
-  "client_secret_value": "<client_secret>",
-  "odata_maxpagesize": 5000
-}

airbyte-source-microsoft-dataverse-0.1.2/integration_tests/sample_state.json

@@ -1,5 +0,0 @@
-{
-  "<entity_name>": {
-    "$deltatoken": "12644418993!10/06/2022 20:06:12"
-  }
-}

airbyte-source-microsoft-dataverse-0.1.2/setup.cfg

@@ -1,97 +0,0 @@
-[metadata]
-name = airbyte-source-microsoft-dataverse
-version = 0.1.2
-author = Airbyte
-author_email = contact@airbyte.io
-long_description = # Microsoft Dataverse Source
-	
-	This is the repository for the Microsoft Dataverse source connector, written in Python.
-	For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/microsoft-dataverse).
-	
-	
-	**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
-	pip install '.[tests]'
-	```
-	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/microsoft-dataverse)
-	to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_microsoft_dataverse/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 `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 microsoft-dataverse 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-microsoft-dataverse build
-	```
-	
-	An image will be built with the tag `airbyte/source-microsoft-dataverse:dev`.
-	
-	**Via `docker build`:**
-	```bash
-	docker build -t airbyte/source-microsoft-dataverse:dev .
-	```
-	
-	Then run any of the connector commands as follows:
-	```
-	docker run --rm airbyte/source-microsoft-dataverse:dev spec
-	docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-microsoft-dataverse:dev check --config /secrets/config.json
-	docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-microsoft-dataverse:dev discover --config /secrets/config.json
-	docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-microsoft-dataverse: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-microsoft-dataverse 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-microsoft-dataverse 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/microsoft-dataverse.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.
-long_description_content_type = text/markdown
-
-[egg_info]
-tag_build = 
-tag_date = 0
-

airbyte-source-microsoft-dataverse-0.1.2/setup.py

@@ -1,43 +0,0 @@
-#
-# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
-#
-
-
-from setuptools import find_packages, setup
-
-MAIN_REQUIREMENTS = [
-    "airbyte-cdk~=0.2",
-]
-
-TEST_REQUIREMENTS = [
-    "requests-mock~=1.9.3",
-    "pytest~=6.1",
-    "pytest-mock~=3.6.1",
-]
-
-setup(
-    entry_points={
-        "console_scripts": [
-            "source-microsoft-dataverse=source_microsoft_dataverse.run:run",
-        ],
-    },
-    description="Source implementation for Microsoft Dataverse.",
-    packages=find_packages(),
-    install_requires=MAIN_REQUIREMENTS,
-    package_data={
-        "": [
-            # Include yaml files in the package (if any)
-            "*.yml",
-            "*.yaml",
-            # Include all json files in the package, up to 4 levels deep
-            "*.json",
-            "*/*.json",
-            "*/*/*.json",
-            "*/*/*/*.json",
-            "*/*/*/*/*.json",
-        ]
-    },
-    extras_require={
-        "tests": TEST_REQUIREMENTS,
-    },
-)

airbyte-source-microsoft-dataverse-0.1.2/unit_tests/__init__.py

@@ -1,3 +0,0 @@
-#
-# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
-#

airbyte-source-microsoft-dataverse-0.1.2/unit_tests/test_dataverse.py

@@ -1,15 +0,0 @@
-#
-# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
-#
-
-import pytest
-from source_microsoft_dataverse.dataverse import AirbyteType, convert_dataverse_type
-
-
-@pytest.mark.parametrize(
-    "dataverse_type,expected_result",
-    [("String", AirbyteType.String.value), ("Integer", AirbyteType.Integer.value), ("Virtual", None), ("Random", AirbyteType.String.value)],
-)
-def test_convert_dataverse_type(dataverse_type, expected_result):
-    result = convert_dataverse_type(dataverse_type)
-    assert result == expected_result

airbyte-source-microsoft-dataverse-0.1.2/unit_tests/test_incremental_streams.py

@@ -1,101 +0,0 @@
-#
-# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
-#
-
-from unittest.mock import MagicMock
-
-from pytest import fixture
-from source_microsoft_dataverse.source import IncrementalMicrosoftDataverseStream
-
-
-@fixture
-def incremental_config():
-    return {
-        "url": "http://test-url",
-        "stream_name": "test_stream",
-        "stream_path": "test_path",
-        "primary_key": [["test_primary_key"]],
-        "schema": {},
-        "odata_maxpagesize": 100,
-        "config_cursor_field": ["test_cursor_field"],
-        "authenticator": MagicMock(),
-    }
-
-
-@fixture
-def incremental_response(incremental_config):
-    return {
-        "@odata.deltaLink": f"{incremental_config['url']}?$deltatoken=12644418993%2110%2F06%2F2022%2020%3A06%3A12",
-        "value": [
-            {"test_primary_key": "pk", "test_cursor_field": "test-date"},
-            {"id": "pk2", "@odata.context": "context", "reason": "deleted"},
-        ],
-    }
-
-
-def test_primary_key(incremental_config):
-    stream = IncrementalMicrosoftDataverseStream(**incremental_config)
-    expected_primary_key = [["test_primary_key"]]
-    assert stream.primary_key == expected_primary_key
-
-
-def test_stream_name(incremental_config):
-    stream = IncrementalMicrosoftDataverseStream(**incremental_config)
-    expected_stream_name = "test_stream"
-    assert stream.name == expected_stream_name
-
-
-def test_stream_path(incremental_config):
-    stream = IncrementalMicrosoftDataverseStream(**incremental_config)
-    expected_stream_path = "test_path"
-    assert stream.path() == expected_stream_path
-
-
-def test_cursor_field(incremental_config):
-    stream = IncrementalMicrosoftDataverseStream(**incremental_config)
-    expected_cursor_field = ["test_cursor_field"]
-    assert stream.cursor_field == expected_cursor_field
-
-
-def test_supports_incremental(incremental_config, mocker):
-    mocker.patch.object(IncrementalMicrosoftDataverseStream, "cursor_field", "dummy_field")
-    stream = IncrementalMicrosoftDataverseStream(**incremental_config)
-    assert stream.supports_incremental
-
-
-def test_source_defined_cursor(incremental_config):
-    stream = IncrementalMicrosoftDataverseStream(**incremental_config)
-    assert stream.source_defined_cursor
-
-
-def test_stream_checkpoint_interval(incremental_config):
-    stream = IncrementalMicrosoftDataverseStream(**incremental_config)
-    expected_checkpoint_interval = None
-    assert stream.state_checkpoint_interval == expected_checkpoint_interval
-
-
-def test_parse_request(incremental_config, incremental_response, mocker):
-    response_mock, datetime_mock = MagicMock(), MagicMock()
-    response_mock.json.return_value = incremental_response
-    datetime_mock.now.return_value.isoformat.return_value = "test-time"
-    mocker.patch("source_microsoft_dataverse.streams.datetime", datetime_mock)
-
-    stream = IncrementalMicrosoftDataverseStream(**incremental_config)
-
-    iterable = stream.parse_response(response_mock)
-    iterable_list = list(iterable)
-    assert len(iterable_list) == 2
-    assert stream.state[stream.delta_token_field] == "12644418993!10/06/2022 20:06:12"
-    assert iterable_list[0]["_ab_cdc_updated_at"] == "test-date"
-    assert iterable_list[1]["_ab_cdc_deleted_at"] == "test-time"
-    assert iterable_list[1][incremental_config["primary_key"][0][0]] == "pk2"
-    assert "id" not in iterable_list[1]
-    assert "reason" not in iterable_list[1]
-    assert "@odata.context" not in iterable_list[1]
-
-
-def test_request_headers(incremental_config):
-    stream = IncrementalMicrosoftDataverseStream(**incremental_config)
-    headers = stream.request_headers(stream_state={})
-    assert "Prefer" in headers
-    assert headers["Prefer"] == "odata.track-changes,odata.maxpagesize=100"

airbyte-source-microsoft-dataverse-0.1.2/unit_tests/test_source.py

@@ -1,148 +0,0 @@
-#
-# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
-#
-
-import json
-from unittest import mock
-from unittest.mock import MagicMock
-
-from airbyte_cdk.models import SyncMode
-from source_microsoft_dataverse.dataverse import AirbyteType
-from source_microsoft_dataverse.source import SourceMicrosoftDataverse
-from source_microsoft_dataverse.streams import IncrementalMicrosoftDataverseStream, MicrosoftDataverseStream
-
-
-@mock.patch("source_microsoft_dataverse.source.do_request")
-def test_check_connection(mock_request):
-    mock_request.return_value.raise_for_status = lambda: ()
-    source = SourceMicrosoftDataverse()
-    logger_mock, config_mock = MagicMock(), MagicMock()
-    assert source.check_connection(logger_mock, config_mock) == (True, None)
-
-
-@mock.patch("source_microsoft_dataverse.source.get_auth")
-@mock.patch("source_microsoft_dataverse.source.do_request")
-def test_streams_incremental(mock_get_auth, mock_request):
-    streams = MagicMock()
-    streams.sync_mode = SyncMode.incremental
-    streams.stream.name = "test"
-
-    catalog = MagicMock()
-
-    catalog.streams = [streams]
-
-    config_mock = MagicMock()
-    source = SourceMicrosoftDataverse()
-    source.catalogs = catalog
-
-    streams = source.streams(config_mock)
-
-    expected_streams_number = 1
-    assert len(streams) == expected_streams_number
-    assert isinstance(streams[0], IncrementalMicrosoftDataverseStream)
-    assert streams[0].name == "test"
-
-
-@mock.patch("source_microsoft_dataverse.source.get_auth")
-@mock.patch("source_microsoft_dataverse.source.do_request")
-def test_streams_full_refresh(mock_get_auth, mock_request):
-    streams = MagicMock()
-    streams.sync_mode = SyncMode.full_refresh
-    streams.stream.name = "test"
-
-    catalog = MagicMock()
-
-    catalog.streams = [streams]
-
-    config_mock = MagicMock()
-    source = SourceMicrosoftDataverse()
-    source.catalogs = catalog
-
-    streams = source.streams(config_mock)
-
-    expected_streams_number = 1
-    assert len(streams) == expected_streams_number
-    assert isinstance(streams[0], MicrosoftDataverseStream)
-    assert streams[0].name == "test"
-
-
-@mock.patch("source_microsoft_dataverse.source.do_request")
-def test_discover_incremental(mock_request):
-    result_json = json.loads(
-        """
-        {
-            "value": [
-                {
-                    "LogicalName": "stream",
-                    "PrimaryIdAttribute": "primary",
-                    "ChangeTrackingEnabled": true,
-                    "CanChangeTrackingBeEnabled": {
-                        "Value": true
-                    },
-                    "Attributes": [
-                        {
-                            "LogicalName": "test",
-                            "AttributeType": "String"
-                        },
-                        {
-                            "LogicalName": "modifiedon",
-                            "AttributeType": "DateTime"
-                        }
-                    ]
-                }
-            ]
-        }
-    """
-    )
-
-    mock_request.return_value.status.return_value = 200
-    mock_request.return_value.json.return_value = result_json
-
-    source = SourceMicrosoftDataverse()
-    logger_mock, config_mock = MagicMock(), MagicMock()
-
-    catalog = source.discover(logger_mock, config_mock)
-
-    assert not {"modifiedon"} ^ set(catalog.streams[0].default_cursor_field)
-    assert not {SyncMode.full_refresh, SyncMode.incremental} ^ set(catalog.streams[0].supported_sync_modes)
-    assert not {"primary"} ^ set(catalog.streams[0].source_defined_primary_key[0])
-    assert catalog.streams[0].json_schema["properties"]["test"] == AirbyteType.String.value
-
-
-@mock.patch("source_microsoft_dataverse.source.do_request")
-def test_discover_full_refresh(mock_request):
-    result_json = json.loads(
-        """
-        {
-            "value": [
-                {
-                    "LogicalName": "stream",
-                    "PrimaryIdAttribute": "primary",
-                    "ChangeTrackingEnabled": false,
-                    "CanChangeTrackingBeEnabled": {
-                        "Value": false
-                    },
-                    "Attributes": [
-                        {
-                            "LogicalName": "test",
-                            "AttributeType": "String"
-                        }
-                    ]
-                }
-            ]
-        }
-    """
-    )
-
-    mock_request.return_value.status.return_value = 200
-    mock_request.return_value.json.return_value = result_json
-
-    source = SourceMicrosoftDataverse()
-    logger_mock, config_mock = MagicMock(), MagicMock()
-
-    catalog = source.discover(logger_mock, config_mock)
-
-    assert catalog.streams[0].default_cursor_field is None or len(catalog.streams[0].default_cursor_field) == 0
-    assert not {SyncMode.full_refresh} ^ set(catalog.streams[0].supported_sync_modes)
-    assert not {"primary"} ^ set(catalog.streams[0].source_defined_primary_key[0])
-    assert catalog.streams[0].json_schema["properties"]["test"] == AirbyteType.String.value

airbyte-source-microsoft-dataverse-0.1.2/unit_tests/test_streams.py

@@ -1,107 +0,0 @@
-#
-# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
-#
-
-from http import HTTPStatus
-from unittest.mock import MagicMock
-
-import pytest
-from pytest import fixture
-from source_microsoft_dataverse.source import MicrosoftDataverseStream
-
-
-@fixture
-def incremental_config():
-    return {
-        "url": "http://test-url",
-        "stream_name": "test_stream",
-        "stream_path": "test_path",
-        "primary_key": [["test_primary_key"]],
-        "schema": {},
-        "odata_maxpagesize": 100,
-        "authenticator": MagicMock(),
-    }
-
-
-@pytest.mark.parametrize(
-    ("inputs", "expected_params"),
-    [
-        ({"stream_slice": None, "stream_state": {}, "next_page_token": None}, {}),
-        ({"stream_slice": None, "stream_state": {}, "next_page_token": {"$skiptoken": "skiptoken"}}, {"$skiptoken": "skiptoken"}),
-        ({"stream_slice": None, "stream_state": {"$deltatoken": "delta"}, "next_page_token": None}, {"$deltatoken": "delta"}),
-    ],
-)
-def test_request_params(inputs, expected_params, incremental_config):
-    stream = MicrosoftDataverseStream(**incremental_config)
-    assert stream.request_params(**inputs) == expected_params
-
-
-@pytest.mark.parametrize(
-    ("response_json", "next_page_token"),
-    [
-        (
-            {
-                "@odata.nextLink": "https://url?$skiptoken=oEBwdSP6uehIAxQOWq_3Ksh_TLol6KIm3stvdc6hGhZRi1hQ7Spe__dpvm3U4zReE4CYXC2zOtaKdi7KHlUtC2CbRiBIUwOxPKLa"
-            },
-            {"$skiptoken": "oEBwdSP6uehIAxQOWq_3Ksh_TLol6KIm3stvdc6hGhZRi1hQ7Spe__dpvm3U4zReE4CYXC2zOtaKdi7KHlUtC2CbRiBIUwOxPKLa"},
-        ),
-        ({"value": []}, None),
-    ],
-)
-def test_next_page_token(response_json, next_page_token, incremental_config):
-    stream = MicrosoftDataverseStream(**incremental_config)
-    response = MagicMock()
-    response.json.return_value = response_json
-    inputs = {"response": response}
-    expected_token = next_page_token
-    assert stream.next_page_token(**inputs) == expected_token
-
-
-def test_parse_response(incremental_config):
-    stream = MicrosoftDataverseStream(**incremental_config)
-    response = MagicMock()
-    response.json.return_value = {"value": [{"test-key": "test-value"}]}
-    inputs = {"response": response}
-    expected_parsed_object = {"test-key": "test-value"}
-    assert next(stream.parse_response(**inputs)) == expected_parsed_object
-
-
-def test_request_headers(incremental_config):
-    stream = MicrosoftDataverseStream(**incremental_config)
-    inputs = {"stream_slice": None, "stream_state": None, "next_page_token": None}
-    expected_headers = {
-        "Cache-Control": "no-cache",
-        "OData-Version": "4.0",
-        "Content-Type": "application/json",
-        "Prefer": "odata.maxpagesize=100",
-    }
-    assert stream.request_headers(**inputs) == expected_headers
-
-
-def test_http_method(incremental_config):
-    stream = MicrosoftDataverseStream(**incremental_config)
-    expected_method = "GET"
-    assert stream.http_method == expected_method
-
-
-@pytest.mark.parametrize(
-    ("http_status", "should_retry"),
-    [
-        (HTTPStatus.OK, False),
-        (HTTPStatus.BAD_REQUEST, False),
-        (HTTPStatus.TOO_MANY_REQUESTS, True),
-        (HTTPStatus.INTERNAL_SERVER_ERROR, True),
-    ],
-)
-def test_should_retry(incremental_config, http_status, should_retry):
-    response_mock = MagicMock()
-    response_mock.status_code = http_status
-    stream = MicrosoftDataverseStream(**incremental_config)
-    assert stream.should_retry(response_mock) == should_retry
-
-
-def test_backoff_time(incremental_config):
-    response_mock = MagicMock()
-    stream = MicrosoftDataverseStream(**incremental_config)
-    expected_backoff_time = None
-    assert stream.backoff_time(response_mock) == expected_backoff_time