airbyte-source-braintree 0.2.1__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (33) hide show
  1. airbyte-source-braintree-0.2.1/PKG-INFO +98 -0
  2. airbyte-source-braintree-0.2.1/README.md +99 -0
  3. airbyte-source-braintree-0.2.1/airbyte_source_braintree.egg-info/PKG-INFO +98 -0
  4. airbyte-source-braintree-0.2.1/airbyte_source_braintree.egg-info/SOURCES.txt +32 -0
  5. airbyte-source-braintree-0.2.1/airbyte_source_braintree.egg-info/dependency_links.txt +1 -0
  6. airbyte-source-braintree-0.2.1/airbyte_source_braintree.egg-info/entry_points.txt +2 -0
  7. airbyte-source-braintree-0.2.1/airbyte_source_braintree.egg-info/requires.txt +6 -0
  8. airbyte-source-braintree-0.2.1/airbyte_source_braintree.egg-info/top_level.txt +2 -0
  9. airbyte-source-braintree-0.2.1/integration_tests/__init__.py +23 -0
  10. airbyte-source-braintree-0.2.1/integration_tests/abnormal_state.json +14 -0
  11. airbyte-source-braintree-0.2.1/integration_tests/acceptance.py +16 -0
  12. airbyte-source-braintree-0.2.1/integration_tests/configured_catalog.json +81 -0
  13. airbyte-source-braintree-0.2.1/integration_tests/configured_catalog_incremental.json +52 -0
  14. airbyte-source-braintree-0.2.1/integration_tests/invalid_config.json +7 -0
  15. airbyte-source-braintree-0.2.1/integration_tests/sample_config.json +7 -0
  16. airbyte-source-braintree-0.2.1/integration_tests/sample_state.json +14 -0
  17. airbyte-source-braintree-0.2.1/integration_tests/spec.json +45 -0
  18. airbyte-source-braintree-0.2.1/setup.cfg +96 -0
  19. airbyte-source-braintree-0.2.1/setup.py +40 -0
  20. airbyte-source-braintree-0.2.1/source_braintree/__init__.py +8 -0
  21. airbyte-source-braintree-0.2.1/source_braintree/manifest.yaml +15978 -0
  22. airbyte-source-braintree-0.2.1/source_braintree/run.py +14 -0
  23. airbyte-source-braintree-0.2.1/source_braintree/schemas/__init__.py +32 -0
  24. airbyte-source-braintree-0.2.1/source_braintree/schemas/cards.py +148 -0
  25. airbyte-source-braintree-0.2.1/source_braintree/schemas/common.py +81 -0
  26. airbyte-source-braintree-0.2.1/source_braintree/schemas/customer.py +47 -0
  27. airbyte-source-braintree-0.2.1/source_braintree/schemas/discount.py +20 -0
  28. airbyte-source-braintree-0.2.1/source_braintree/schemas/dispute.py +48 -0
  29. airbyte-source-braintree-0.2.1/source_braintree/schemas/merchant_account.py +42 -0
  30. airbyte-source-braintree-0.2.1/source_braintree/schemas/plan.py +28 -0
  31. airbyte-source-braintree-0.2.1/source_braintree/schemas/subscription.py +42 -0
  32. airbyte-source-braintree-0.2.1/source_braintree/schemas/transaction.py +122 -0
  33. airbyte-source-braintree-0.2.1/source_braintree/source.py +186 -0
@@ -0,0 +1,98 @@
1
+ Metadata-Version: 2.1
2
+ Name: airbyte-source-braintree
3
+ Version: 0.2.1
4
+ Summary: Source implementation for Braintree No Code.
5
+ Author: Airbyte
6
+ Author-email: contact@airbyte.io
7
+ Description-Content-Type: text/markdown
8
+ Requires-Dist: airbyte-cdk~=0.1
9
+ Requires-Dist: braintree~=4.21.0
10
+ Provides-Extra: tests
11
+ Requires-Dist: pytest~=6.2; extra == "tests"
12
+ Requires-Dist: pytest-mock~=3.6.1; extra == "tests"
13
+
14
+ # Braintree Source
15
+
16
+ This is the repository for the Braintree source connector, written in Python.
17
+ For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/braintree).
18
+
19
+
20
+ **To iterate on this connector, make sure to complete this prerequisites section.**
21
+
22
+
23
+ From this connector directory, create a virtual environment:
24
+ ```
25
+ python -m venv .venv
26
+ ```
27
+
28
+ This will generate a virtualenv for this module in `.venv/`. Make sure this venv is active in your
29
+ development environment of choice. To activate it from the terminal, run:
30
+ ```
31
+ source .venv/bin/activate
32
+ pip install -r requirements.txt
33
+ ```
34
+ If you are in an IDE, follow your IDE's instructions to activate the virtualenv.
35
+
36
+ Note that while we are installing dependencies from `requirements.txt`, you should only edit `setup.py` for your dependencies. `requirements.txt` is
37
+ used for editable installs (`pip install -e`) to pull in Python dependencies from the monorepo and will call `setup.py`.
38
+ 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
39
+ should work as you expect.
40
+
41
+ **If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/braintree)
42
+ to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_braintree/spec.json` file.
43
+ Note that the `secrets` directory is gitignored by default, so there is no danger of accidentally checking in sensitive information.
44
+ See `integration_tests/sample_config.json` for a sample config file.
45
+
46
+ **If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source braintree test creds`
47
+ and place them into `secrets/config.json`.
48
+
49
+ ```
50
+ python main.py spec
51
+ python main.py check --config secrets/config.json
52
+ python main.py discover --config secrets/config.json
53
+ python main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.json
54
+ ```
55
+
56
+
57
+
58
+ **Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**
59
+ ```bash
60
+ airbyte-ci connectors --name=source-braintree build
61
+ ```
62
+
63
+ An image will be built with the tag `airbyte/source-braintree:dev`.
64
+
65
+ **Via `docker build`:**
66
+ ```bash
67
+ docker build -t airbyte/source-braintree:dev .
68
+ ```
69
+
70
+ Then run any of the connector commands as follows:
71
+ ```
72
+ docker run --rm airbyte/source-braintree:dev spec
73
+ docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-braintree:dev check --config /secrets/config.json
74
+ docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-braintree:dev discover --config /secrets/config.json
75
+ docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-braintree:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
76
+ ```
77
+
78
+ You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
79
+ ```bash
80
+ airbyte-ci connectors --name=source-braintree test
81
+ ```
82
+
83
+ 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.
84
+ 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.
85
+
86
+ All of your dependencies should go in `setup.py`, NOT `requirements.txt`. The requirements file is only used to connect internal Airbyte dependencies in the monorepo for local development.
87
+ We split dependencies between two groups, dependencies that are:
88
+ * required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
89
+ * required for the testing need to go to `TEST_REQUIREMENTS` list
90
+
91
+ You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
92
+ 1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-braintree test`
93
+ 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).
94
+ 3. Make sure the `metadata.yaml` content is up to date.
95
+ 4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/braintree.md`).
96
+ 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).
97
+ 6. Pat yourself on the back for being an awesome contributor.
98
+ 7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
@@ -0,0 +1,99 @@
1
+ # Braintree Source
2
+
3
+ This is the repository for the Braintree source connector, written in Python.
4
+ For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/braintree).
5
+
6
+ ## Local development
7
+
8
+ ### Prerequisites
9
+ **To iterate on this connector, make sure to complete this prerequisites section.**
10
+
11
+ #### Minimum Python version required `= 3.7.0`
12
+
13
+ #### Build & Activate Virtual Environment and install dependencies
14
+ From this connector directory, create a virtual environment:
15
+ ```
16
+ python -m venv .venv
17
+ ```
18
+
19
+ This will generate a virtualenv for this module in `.venv/`. Make sure this venv is active in your
20
+ development environment of choice. To activate it from the terminal, run:
21
+ ```
22
+ source .venv/bin/activate
23
+ pip install -r requirements.txt
24
+ ```
25
+ If you are in an IDE, follow your IDE's instructions to activate the virtualenv.
26
+
27
+ Note that while we are installing dependencies from `requirements.txt`, you should only edit `setup.py` for your dependencies. `requirements.txt` is
28
+ used for editable installs (`pip install -e`) to pull in Python dependencies from the monorepo and will call `setup.py`.
29
+ 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
30
+ should work as you expect.
31
+
32
+ #### Create credentials
33
+ **If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/braintree)
34
+ to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_braintree/spec.json` file.
35
+ Note that the `secrets` directory is gitignored by default, so there is no danger of accidentally checking in sensitive information.
36
+ See `integration_tests/sample_config.json` for a sample config file.
37
+
38
+ **If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source braintree test creds`
39
+ and place them into `secrets/config.json`.
40
+
41
+ ### Locally running the connector
42
+ ```
43
+ python main.py spec
44
+ python main.py check --config secrets/config.json
45
+ python main.py discover --config secrets/config.json
46
+ python main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.json
47
+ ```
48
+
49
+ ### Locally running the connector docker image
50
+
51
+
52
+ #### Build
53
+ **Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**
54
+ ```bash
55
+ airbyte-ci connectors --name=source-braintree build
56
+ ```
57
+
58
+ An image will be built with the tag `airbyte/source-braintree:dev`.
59
+
60
+ **Via `docker build`:**
61
+ ```bash
62
+ docker build -t airbyte/source-braintree:dev .
63
+ ```
64
+
65
+ #### Run
66
+ Then run any of the connector commands as follows:
67
+ ```
68
+ docker run --rm airbyte/source-braintree:dev spec
69
+ docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-braintree:dev check --config /secrets/config.json
70
+ docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-braintree:dev discover --config /secrets/config.json
71
+ docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-braintree:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
72
+ ```
73
+
74
+ ## Testing
75
+ You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
76
+ ```bash
77
+ airbyte-ci connectors --name=source-braintree test
78
+ ```
79
+
80
+ ### Customizing acceptance Tests
81
+ 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.
82
+ 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.
83
+
84
+ ## Dependency Management
85
+ 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.
86
+ We split dependencies between two groups, dependencies that are:
87
+ * required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
88
+ * required for the testing need to go to `TEST_REQUIREMENTS` list
89
+
90
+ ### Publishing a new version of the connector
91
+ You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
92
+ 1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-braintree test`
93
+ 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).
94
+ 3. Make sure the `metadata.yaml` content is up to date.
95
+ 4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/braintree.md`).
96
+ 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).
97
+ 6. Pat yourself on the back for being an awesome contributor.
98
+ 7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
99
+
@@ -0,0 +1,98 @@
1
+ Metadata-Version: 2.1
2
+ Name: airbyte-source-braintree
3
+ Version: 0.2.1
4
+ Summary: Source implementation for Braintree No Code.
5
+ Author: Airbyte
6
+ Author-email: contact@airbyte.io
7
+ Description-Content-Type: text/markdown
8
+ Requires-Dist: airbyte-cdk~=0.1
9
+ Requires-Dist: braintree~=4.21.0
10
+ Provides-Extra: tests
11
+ Requires-Dist: pytest~=6.2; extra == "tests"
12
+ Requires-Dist: pytest-mock~=3.6.1; extra == "tests"
13
+
14
+ # Braintree Source
15
+
16
+ This is the repository for the Braintree source connector, written in Python.
17
+ For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/braintree).
18
+
19
+
20
+ **To iterate on this connector, make sure to complete this prerequisites section.**
21
+
22
+
23
+ From this connector directory, create a virtual environment:
24
+ ```
25
+ python -m venv .venv
26
+ ```
27
+
28
+ This will generate a virtualenv for this module in `.venv/`. Make sure this venv is active in your
29
+ development environment of choice. To activate it from the terminal, run:
30
+ ```
31
+ source .venv/bin/activate
32
+ pip install -r requirements.txt
33
+ ```
34
+ If you are in an IDE, follow your IDE's instructions to activate the virtualenv.
35
+
36
+ Note that while we are installing dependencies from `requirements.txt`, you should only edit `setup.py` for your dependencies. `requirements.txt` is
37
+ used for editable installs (`pip install -e`) to pull in Python dependencies from the monorepo and will call `setup.py`.
38
+ 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
39
+ should work as you expect.
40
+
41
+ **If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/braintree)
42
+ to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_braintree/spec.json` file.
43
+ Note that the `secrets` directory is gitignored by default, so there is no danger of accidentally checking in sensitive information.
44
+ See `integration_tests/sample_config.json` for a sample config file.
45
+
46
+ **If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source braintree test creds`
47
+ and place them into `secrets/config.json`.
48
+
49
+ ```
50
+ python main.py spec
51
+ python main.py check --config secrets/config.json
52
+ python main.py discover --config secrets/config.json
53
+ python main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.json
54
+ ```
55
+
56
+
57
+
58
+ **Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**
59
+ ```bash
60
+ airbyte-ci connectors --name=source-braintree build
61
+ ```
62
+
63
+ An image will be built with the tag `airbyte/source-braintree:dev`.
64
+
65
+ **Via `docker build`:**
66
+ ```bash
67
+ docker build -t airbyte/source-braintree:dev .
68
+ ```
69
+
70
+ Then run any of the connector commands as follows:
71
+ ```
72
+ docker run --rm airbyte/source-braintree:dev spec
73
+ docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-braintree:dev check --config /secrets/config.json
74
+ docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-braintree:dev discover --config /secrets/config.json
75
+ docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-braintree:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
76
+ ```
77
+
78
+ You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
79
+ ```bash
80
+ airbyte-ci connectors --name=source-braintree test
81
+ ```
82
+
83
+ 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.
84
+ 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.
85
+
86
+ All of your dependencies should go in `setup.py`, NOT `requirements.txt`. The requirements file is only used to connect internal Airbyte dependencies in the monorepo for local development.
87
+ We split dependencies between two groups, dependencies that are:
88
+ * required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
89
+ * required for the testing need to go to `TEST_REQUIREMENTS` list
90
+
91
+ You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
92
+ 1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-braintree test`
93
+ 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).
94
+ 3. Make sure the `metadata.yaml` content is up to date.
95
+ 4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/braintree.md`).
96
+ 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).
97
+ 6. Pat yourself on the back for being an awesome contributor.
98
+ 7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
@@ -0,0 +1,32 @@
1
+ README.md
2
+ setup.cfg
3
+ setup.py
4
+ airbyte_source_braintree.egg-info/PKG-INFO
5
+ airbyte_source_braintree.egg-info/SOURCES.txt
6
+ airbyte_source_braintree.egg-info/dependency_links.txt
7
+ airbyte_source_braintree.egg-info/entry_points.txt
8
+ airbyte_source_braintree.egg-info/requires.txt
9
+ airbyte_source_braintree.egg-info/top_level.txt
10
+ integration_tests/__init__.py
11
+ integration_tests/abnormal_state.json
12
+ integration_tests/acceptance.py
13
+ integration_tests/configured_catalog.json
14
+ integration_tests/configured_catalog_incremental.json
15
+ integration_tests/invalid_config.json
16
+ integration_tests/sample_config.json
17
+ integration_tests/sample_state.json
18
+ integration_tests/spec.json
19
+ source_braintree/__init__.py
20
+ source_braintree/manifest.yaml
21
+ source_braintree/run.py
22
+ source_braintree/source.py
23
+ source_braintree/schemas/__init__.py
24
+ source_braintree/schemas/cards.py
25
+ source_braintree/schemas/common.py
26
+ source_braintree/schemas/customer.py
27
+ source_braintree/schemas/discount.py
28
+ source_braintree/schemas/dispute.py
29
+ source_braintree/schemas/merchant_account.py
30
+ source_braintree/schemas/plan.py
31
+ source_braintree/schemas/subscription.py
32
+ source_braintree/schemas/transaction.py
@@ -0,0 +1,2 @@
1
+ [console_scripts]
2
+ source-braintree = source_braintree.run:run
@@ -0,0 +1,6 @@
1
+ airbyte-cdk~=0.1
2
+ braintree~=4.21.0
3
+
4
+ [tests]
5
+ pytest~=6.2
6
+ pytest-mock~=3.6.1
@@ -0,0 +1,2 @@
1
+ integration_tests
2
+ source_braintree
@@ -0,0 +1,23 @@
1
+ #
2
+ # MIT License
3
+ #
4
+ # Copyright (c) 2020 Airbyte
5
+ #
6
+ # Permission is hereby granted, free of charge, to any person obtaining a copy
7
+ # of this software and associated documentation files (the "Software"), to deal
8
+ # in the Software without restriction, including without limitation the rights
9
+ # to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
10
+ # copies of the Software, and to permit persons to whom the Software is
11
+ # furnished to do so, subject to the following conditions:
12
+ #
13
+ # The above copyright notice and this permission notice shall be included in all
14
+ # copies or substantial portions of the Software.
15
+ #
16
+ # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
17
+ # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
18
+ # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
19
+ # AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
20
+ # LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
21
+ # OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
22
+ # SOFTWARE.
23
+ #
@@ -0,0 +1,14 @@
1
+ {
2
+ "customer_stream": {
3
+ "created_at": "2222-01-01 00:00:00"
4
+ },
5
+ "dispute_stream": {
6
+ "received_date": "2222-01-01 00:00:00"
7
+ },
8
+ "transaction_stream": {
9
+ "created_at": "2222-01-01 00:00:00"
10
+ },
11
+ "subscription_stream": {
12
+ "created_at": "2222-01-01 00:00:00"
13
+ }
14
+ }
@@ -0,0 +1,16 @@
1
+ #
2
+ # Copyright (c) 2023 Airbyte, Inc., all rights reserved.
3
+ #
4
+
5
+
6
+ import pytest
7
+
8
+ pytest_plugins = ("connector_acceptance_test.plugin",)
9
+
10
+
11
+ @pytest.fixture(scope="session", autouse=True)
12
+ def connector_setup():
13
+ """This fixture is a placeholder for external resources that acceptance test might require."""
14
+ # TODO: setup test dependencies
15
+ yield
16
+ # TODO: clean up test dependencies
@@ -0,0 +1,81 @@
1
+ {
2
+ "streams": [
3
+ {
4
+ "stream": {
5
+ "name": "customer_stream",
6
+ "json_schema": {},
7
+ "supported_sync_modes": ["full_refresh", "incremental"],
8
+ "source_defined_cursor": false,
9
+ "source_defined_primary_key": [["id"]]
10
+ },
11
+ "sync_mode": "full_refresh",
12
+ "destination_sync_mode": "overwrite"
13
+ },
14
+ {
15
+ "stream": {
16
+ "name": "discount_stream",
17
+ "json_schema": {},
18
+ "supported_sync_modes": ["full_refresh"],
19
+ "source_defined_cursor": false,
20
+ "source_defined_primary_key": [["id"]]
21
+ },
22
+ "sync_mode": "full_refresh",
23
+ "destination_sync_mode": "overwrite"
24
+ },
25
+ {
26
+ "stream": {
27
+ "name": "dispute_stream",
28
+ "json_schema": {},
29
+ "supported_sync_modes": ["full_refresh"],
30
+ "source_defined_cursor": false,
31
+ "source_defined_primary_key": [["id"]]
32
+ },
33
+ "sync_mode": "full_refresh",
34
+ "destination_sync_mode": "overwrite"
35
+ },
36
+ {
37
+ "stream": {
38
+ "name": "transaction_stream",
39
+ "json_schema": {},
40
+ "supported_sync_modes": ["full_refresh", "incremental"],
41
+ "source_defined_cursor": false,
42
+ "source_defined_primary_key": [["id"]]
43
+ },
44
+ "sync_mode": "full_refresh",
45
+ "destination_sync_mode": "overwrite"
46
+ },
47
+ {
48
+ "stream": {
49
+ "name": "merchant_account_stream",
50
+ "json_schema": {},
51
+ "supported_sync_modes": ["full_refresh"],
52
+ "source_defined_cursor": false,
53
+ "source_defined_primary_key": [["id"]]
54
+ },
55
+ "sync_mode": "full_refresh",
56
+ "destination_sync_mode": "overwrite"
57
+ },
58
+ {
59
+ "stream": {
60
+ "name": "plan_stream",
61
+ "json_schema": {},
62
+ "supported_sync_modes": ["full_refresh"],
63
+ "source_defined_cursor": false,
64
+ "source_defined_primary_key": [["id"]]
65
+ },
66
+ "sync_mode": "full_refresh",
67
+ "destination_sync_mode": "overwrite"
68
+ },
69
+ {
70
+ "stream": {
71
+ "name": "subscription_stream",
72
+ "json_schema": {},
73
+ "supported_sync_modes": ["full_refresh", "incremental"],
74
+ "source_defined_cursor": false,
75
+ "source_defined_primary_key": [["id"]]
76
+ },
77
+ "sync_mode": "full_refresh",
78
+ "destination_sync_mode": "overwrite"
79
+ }
80
+ ]
81
+ }
@@ -0,0 +1,52 @@
1
+ {
2
+ "streams": [
3
+ {
4
+ "stream": {
5
+ "name": "customer_stream",
6
+ "json_schema": {},
7
+ "supported_sync_modes": ["full_refresh", "incremental"],
8
+ "source_defined_cursor": false,
9
+ "default_cursor_field": ["created_at"],
10
+ "source_defined_primary_key": [["id"]]
11
+ },
12
+ "sync_mode": "incremental",
13
+ "destination_sync_mode": "overwrite"
14
+ },
15
+ {
16
+ "stream": {
17
+ "name": "dispute_stream",
18
+ "json_schema": {},
19
+ "supported_sync_modes": ["full_refresh", "incremental"],
20
+ "source_defined_cursor": false,
21
+ "default_cursor_field": ["received_date"],
22
+ "source_defined_primary_key": [["id"]]
23
+ },
24
+ "sync_mode": "incremental",
25
+ "destination_sync_mode": "overwrite"
26
+ },
27
+ {
28
+ "stream": {
29
+ "name": "transaction_stream",
30
+ "json_schema": {},
31
+ "supported_sync_modes": ["full_refresh", "incremental"],
32
+ "source_defined_cursor": false,
33
+ "default_cursor_field": ["created_at"],
34
+ "source_defined_primary_key": [["id"]]
35
+ },
36
+ "sync_mode": "incremental",
37
+ "destination_sync_mode": "overwrite"
38
+ },
39
+ {
40
+ "stream": {
41
+ "name": "subscription_stream",
42
+ "json_schema": {},
43
+ "supported_sync_modes": ["full_refresh", "incremental"],
44
+ "source_defined_cursor": false,
45
+ "default_cursor_field": ["created_at"],
46
+ "source_defined_primary_key": [["id"]]
47
+ },
48
+ "sync_mode": "incremental",
49
+ "destination_sync_mode": "overwrite"
50
+ }
51
+ ]
52
+ }
@@ -0,0 +1,7 @@
1
+ {
2
+ "merchant_id": "merchant id",
3
+ "public_key": "public key",
4
+ "start_date": "asdad as as ",
5
+ "private_key": "private key",
6
+ "environment": "Sandbox"
7
+ }
@@ -0,0 +1,7 @@
1
+ {
2
+ "merchant_id": "merchant id",
3
+ "public_key": "public key",
4
+ "start_date": "2020-11-22T20:32:05Z",
5
+ "private_key": "private key",
6
+ "environment": "Sandbox"
7
+ }
@@ -0,0 +1,14 @@
1
+ {
2
+ "customer_stream": {
3
+ "created_at": "2023-08-08 00:00:00"
4
+ },
5
+ "dispute_stream": {
6
+ "received_date": "2023-08-08 00:00:00"
7
+ },
8
+ "transaction_stream": {
9
+ "created_at": "2023-08-08 00:00:00"
10
+ },
11
+ "subscription_stream": {
12
+ "created_at": "2023-08-08 00:00:00"
13
+ }
14
+ }
@@ -0,0 +1,45 @@
1
+ {
2
+ "documentationUrl": "https://docs.airbyte.com/integrations/sources/braintree",
3
+ "connectionSpecification": {
4
+ "title": "Braintree Spec",
5
+ "type": "object",
6
+ "properties": {
7
+ "merchant_id": {
8
+ "title": "Merchant ID",
9
+ "description": "The unique identifier for your entire gateway account. See the <a href=\"https://docs.airbyte.com/integrations/sources/braintree\">docs</a> for more information on how to obtain this ID.",
10
+ "name": "Merchant ID",
11
+ "type": "string"
12
+ },
13
+ "public_key": {
14
+ "title": "Public Key",
15
+ "description": "Braintree Public Key. See the <a href=\"https://docs.airbyte.com/integrations/sources/braintree\">docs</a> for more information on how to obtain this key.",
16
+ "name": "Public Key",
17
+ "type": "string"
18
+ },
19
+ "private_key": {
20
+ "title": "Private Key",
21
+ "description": "Braintree Private Key. See the <a href=\"https://docs.airbyte.com/integrations/sources/braintree\">docs</a> for more information on how to obtain this key.",
22
+ "name": "Private Key",
23
+ "airbyte_secret": true,
24
+ "type": "string"
25
+ },
26
+ "start_date": {
27
+ "title": "Start Date",
28
+ "description": "UTC date and time in the format 2017-01-25T00:00:00Z. Any data before this date will not be replicated.",
29
+ "name": "Start Date",
30
+ "examples": ["2020", "2020-12-30", "2020-11-22 20:20:05"],
31
+ "type": "string",
32
+ "format": "date-time"
33
+ },
34
+ "environment": {
35
+ "title": "Environment",
36
+ "description": "Environment specifies where the data will come from.",
37
+ "name": "Environment",
38
+ "examples": ["sandbox", "production", "qa", "development"],
39
+ "enum": ["Development", "Sandbox", "Qa", "Production"],
40
+ "type": "string"
41
+ }
42
+ },
43
+ "required": ["merchant_id", "public_key", "private_key", "environment"]
44
+ }
45
+ }