airbyte-source-microsoft-dataverse 0.1.2__tar.gz

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

@@ -0,0 +1,99 @@
+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

@@ -0,0 +1,100 @@
+# 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

@@ -0,0 +1,99 @@
+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

@@ -0,0 +1,27 @@
+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

@@ -0,0 +1 @@
+

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

@@ -0,0 +1,2 @@
+[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

@@ -0,0 +1,6 @@
+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

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

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

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

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

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

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

@@ -0,0 +1,16 @@
+#
+# 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

@@ -0,0 +1,15 @@
+{
+  "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

@@ -0,0 +1,7 @@
+{
+  "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

@@ -0,0 +1,7 @@
+{
+  "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

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

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

@@ -0,0 +1,97 @@
+[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

@@ -0,0 +1,43 @@
+#
+# 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/source_microsoft_dataverse/__init__.py

@@ -0,0 +1,8 @@
+#
+# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
+#
+
+
+from .source import SourceMicrosoftDataverse
+
+__all__ = ["SourceMicrosoftDataverse"]

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

@@ -0,0 +1,80 @@
+#
+# Copyright (c) 2023 Airbyte, Inc., all rights reserved.
+#
+
+from enum import Enum
+from typing import Any, Mapping, MutableMapping, Optional
+
+import requests
+from airbyte_cdk.sources.streams.http.requests_native_auth.oauth import Oauth2Authenticator
+
+
+class MicrosoftOauth2Authenticator(Oauth2Authenticator):
+    def build_refresh_request_body(self) -> Mapping[str, Any]:
+        """
+        Returns the request body to set on the refresh request
+        """
+        payload: MutableMapping[str, Any] = {
+            "grant_type": "client_credentials",
+            "client_id": self.get_client_id(),
+            "client_secret": self.get_client_secret(),
+            "scope": self.get_scopes(),
+        }
+
+        return payload
+
+
+class AirbyteType(Enum):
+
+    String = {"type": ["null", "string"]}
+    Boolean = {"type": ["null", "boolean"]}
+    Timestamp = {"type": ["null", "string"], "format": "date-time", "airbyte_type": "timestamp_with_timezone"}
+    Integer = {"type": ["null", "integer"]}
+    Number = {"type": ["null", "number"]}
+
+
+class DataverseType(Enum):
+
+    String = AirbyteType.String
+    Uniqueidentifier = AirbyteType.String
+    DateTime = AirbyteType.Timestamp
+    Integer = AirbyteType.Integer
+    BigInt = AirbyteType.Integer
+    Money = AirbyteType.Number
+    Boolean = AirbyteType.Boolean
+    Double = AirbyteType.Number
+    Decimal = AirbyteType.Number
+    Status = AirbyteType.Integer
+    State = AirbyteType.Integer
+    Picklist = AirbyteType.Integer
+    Lookup = AirbyteType.String
+    Virtual = None
+
+
+def get_auth(config: Mapping[str, Any]) -> MicrosoftOauth2Authenticator:
+    return MicrosoftOauth2Authenticator(
+        token_refresh_endpoint=f'https://login.microsoftonline.com/{config["tenant_id"]}/oauth2/v2.0/token',
+        client_id=config["client_id"],
+        client_secret=config["client_secret_value"],
+        scopes=[f'{config["url"]}/.default'],
+        refresh_token="",
+    )
+
+
+def do_request(config: Mapping[str, Any], path: str):
+    auth = get_auth(config)
+    headers = auth.get_auth_header()
+    # Call a protected API with the access token.
+    return requests.get(
+        config["url"] + "/api/data/v9.2/" + path,
+        headers=headers,
+    )
+
+
+def convert_dataverse_type(dataverse_type: str) -> Optional[dict]:
+    if dataverse_type in DataverseType.__members__:
+        enum_type = DataverseType[dataverse_type]
+        if enum_type:
+            return enum_type.value if enum_type.value is None else enum_type.value.value
+
+    return AirbyteType.String.value