airbyte-source-okta 0.1.16__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 (32) hide show
  1. airbyte-source-okta-0.1.16/PKG-INFO +110 -0
  2. airbyte-source-okta-0.1.16/README.md +109 -0
  3. airbyte-source-okta-0.1.16/airbyte_source_okta.egg-info/PKG-INFO +110 -0
  4. airbyte-source-okta-0.1.16/airbyte_source_okta.egg-info/SOURCES.txt +31 -0
  5. airbyte-source-okta-0.1.16/airbyte_source_okta.egg-info/dependency_links.txt +1 -0
  6. airbyte-source-okta-0.1.16/airbyte_source_okta.egg-info/entry_points.txt +2 -0
  7. airbyte-source-okta-0.1.16/airbyte_source_okta.egg-info/requires.txt +7 -0
  8. airbyte-source-okta-0.1.16/airbyte_source_okta.egg-info/top_level.txt +2 -0
  9. airbyte-source-okta-0.1.16/integration_tests/__init__.py +3 -0
  10. airbyte-source-okta-0.1.16/integration_tests/abnormal_state.json +57 -0
  11. airbyte-source-okta-0.1.16/integration_tests/acceptance.py +15 -0
  12. airbyte-source-okta-0.1.16/integration_tests/catalog.json +80 -0
  13. airbyte-source-okta-0.1.16/integration_tests/configured_catalog.json +96 -0
  14. airbyte-source-okta-0.1.16/integration_tests/incremental_configured_catalog.json +37 -0
  15. airbyte-source-okta-0.1.16/integration_tests/invalid_config.json +8 -0
  16. airbyte-source-okta-0.1.16/setup.cfg +107 -0
  17. airbyte-source-okta-0.1.16/setup.py +44 -0
  18. airbyte-source-okta-0.1.16/source_okta/__init__.py +30 -0
  19. airbyte-source-okta-0.1.16/source_okta/authenticator.py +30 -0
  20. airbyte-source-okta-0.1.16/source_okta/run.py +14 -0
  21. airbyte-source-okta-0.1.16/source_okta/schemas/custom_roles.json +53 -0
  22. airbyte-source-okta-0.1.16/source_okta/schemas/group_members.json +215 -0
  23. airbyte-source-okta-0.1.16/source_okta/schemas/group_role_assignments.json +87 -0
  24. airbyte-source-okta-0.1.16/source_okta/schemas/groups.json +43 -0
  25. airbyte-source-okta-0.1.16/source_okta/schemas/logs.json +269 -0
  26. airbyte-source-okta-0.1.16/source_okta/schemas/permissions.json +96 -0
  27. airbyte-source-okta-0.1.16/source_okta/schemas/resource_sets.json +71 -0
  28. airbyte-source-okta-0.1.16/source_okta/schemas/user_role_assignments.json +87 -0
  29. airbyte-source-okta-0.1.16/source_okta/schemas/users.json +216 -0
  30. airbyte-source-okta-0.1.16/source_okta/source.py +380 -0
  31. airbyte-source-okta-0.1.16/source_okta/spec.json +84 -0
  32. airbyte-source-okta-0.1.16/source_okta/utils.py +81 -0
@@ -0,0 +1,110 @@
1
+ Metadata-Version: 2.1
2
+ Name: airbyte-source-okta
3
+ Version: 0.1.16
4
+ Summary: Source implementation for Okta.
5
+ Author: Airbyte
6
+ Author-email: contact@airbyte.io
7
+ Description-Content-Type: text/markdown
8
+ Requires-Dist: airbyte-cdk
9
+ Requires-Dist: pendulum==1.2.0
10
+ Provides-Extra: tests
11
+ Requires-Dist: pytest~=6.1; extra == "tests"
12
+ Requires-Dist: pytest-mock~=3.6.1; extra == "tests"
13
+ Requires-Dist: requests-mock; extra == "tests"
14
+
15
+ # Okta Source
16
+
17
+ This is the repository for the Okta source connector, written in Python.
18
+ For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/okta).
19
+
20
+
21
+
22
+ **To iterate on this connector, make sure to complete this prerequisites section.**
23
+
24
+
25
+ From this connector directory, create a virtual environment:
26
+
27
+ ```shell
28
+ python -m venv .venv
29
+ ```
30
+
31
+ This will generate a virtualenv for this module in `.venv/`. Make sure this venv is active in your
32
+ development environment of choice. To activate it from the terminal, run:
33
+
34
+ ```shell
35
+ source .venv/bin/activate
36
+ pip install -r requirements.txt
37
+ ```
38
+
39
+ If you are in an IDE, follow your IDE's instructions to activate the virtualenv.
40
+
41
+ Note that while we are installing dependencies from `requirements.txt`, you should only edit `setup.py` for your dependencies. `requirements.txt` is
42
+ used for editable installs (`pip install -e`) to pull in Python dependencies from the monorepo and will call `setup.py`.
43
+ 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
44
+ should work as you expect.
45
+
46
+
47
+ **If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/okta)
48
+ to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_okta/spec.json` file.
49
+ Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
50
+ See `integration_tests/sample_config.json` for a sample config file.
51
+
52
+ **If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source okta test creds`
53
+ and place them into `secrets/config.json`.
54
+
55
+
56
+ ```shell
57
+ python main.py spec
58
+ python main.py check --config secrets/config.json
59
+ python main.py discover --config secrets/config.json
60
+ python main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.json
61
+ ```
62
+
63
+
64
+
65
+ **Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**
66
+ ```bash
67
+ airbyte-ci connectors --name=source-okta build
68
+ ```
69
+
70
+ An image will be built with the tag `airbyte/source-okta:dev`.
71
+
72
+ **Via `docker build`:**
73
+ ```bash
74
+ docker build -t airbyte/source-okta:dev .
75
+ ```
76
+
77
+
78
+ Then run any of the connector commands as follows:
79
+
80
+ ```shell
81
+ docker run --rm airbyte/source-okta:dev spec
82
+ docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-okta:dev check --config /secrets/config.json
83
+ docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-okta:dev discover --config /secrets/config.json
84
+ docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-okta:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
85
+ ```
86
+
87
+
88
+ You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
89
+ ```bash
90
+ airbyte-ci connectors --name=source-okta test
91
+ ```
92
+
93
+ 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.
94
+ 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.
95
+
96
+
97
+ 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.
98
+ We split dependencies between two groups, dependencies that are:
99
+
100
+ * required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
101
+ * required for the testing need to go to `TEST_REQUIREMENTS` list
102
+
103
+ You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
104
+ 1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-okta test`
105
+ 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).
106
+ 3. Make sure the `metadata.yaml` content is up to date.
107
+ 4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/okta.md`).
108
+ 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).
109
+ 6. Pat yourself on the back for being an awesome contributor.
110
+ 7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
@@ -0,0 +1,109 @@
1
+ # Okta Source
2
+
3
+ This is the repository for the Okta 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/okta).
5
+
6
+ ## Local development
7
+
8
+ ### Prerequisites
9
+
10
+ **To iterate on this connector, make sure to complete this prerequisites section.**
11
+
12
+ #### Build & Activate Virtual Environment and install dependencies
13
+
14
+ From this connector directory, create a virtual environment:
15
+
16
+ ```shell
17
+ python -m venv .venv
18
+ ```
19
+
20
+ This will generate a virtualenv for this module in `.venv/`. Make sure this venv is active in your
21
+ development environment of choice. To activate it from the terminal, run:
22
+
23
+ ```shell
24
+ source .venv/bin/activate
25
+ pip install -r requirements.txt
26
+ ```
27
+
28
+ If you are in an IDE, follow your IDE's instructions to activate the virtualenv.
29
+
30
+ Note that while we are installing dependencies from `requirements.txt`, you should only edit `setup.py` for your dependencies. `requirements.txt` is
31
+ used for editable installs (`pip install -e`) to pull in Python dependencies from the monorepo and will call `setup.py`.
32
+ 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
33
+ should work as you expect.
34
+
35
+ #### Create credentials
36
+
37
+ **If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/okta)
38
+ to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_okta/spec.json` file.
39
+ Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
40
+ See `integration_tests/sample_config.json` for a sample config file.
41
+
42
+ **If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source okta test creds`
43
+ and place them into `secrets/config.json`.
44
+
45
+ ### Locally running the connector
46
+
47
+ ```shell
48
+ python main.py spec
49
+ python main.py check --config secrets/config.json
50
+ python main.py discover --config secrets/config.json
51
+ python main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.json
52
+ ```
53
+
54
+ ### Locally running the connector docker image
55
+
56
+
57
+ #### Build
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-okta build
61
+ ```
62
+
63
+ An image will be built with the tag `airbyte/source-okta:dev`.
64
+
65
+ **Via `docker build`:**
66
+ ```bash
67
+ docker build -t airbyte/source-okta:dev .
68
+ ```
69
+
70
+ #### Run
71
+
72
+ Then run any of the connector commands as follows:
73
+
74
+ ```shell
75
+ docker run --rm airbyte/source-okta:dev spec
76
+ docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-okta:dev check --config /secrets/config.json
77
+ docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-okta:dev discover --config /secrets/config.json
78
+ docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-okta:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
79
+ ```
80
+
81
+
82
+ ## Testing
83
+ You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
84
+ ```bash
85
+ airbyte-ci connectors --name=source-okta test
86
+ ```
87
+
88
+ ### Customizing acceptance Tests
89
+ 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.
90
+ 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.
91
+
92
+ ## Dependency Management
93
+
94
+ 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.
95
+ We split dependencies between two groups, dependencies that are:
96
+
97
+ * required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
98
+ * required for the testing need to go to `TEST_REQUIREMENTS` list
99
+
100
+ ### Publishing a new version of the connector
101
+ You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
102
+ 1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-okta test`
103
+ 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).
104
+ 3. Make sure the `metadata.yaml` content is up to date.
105
+ 4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/okta.md`).
106
+ 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).
107
+ 6. Pat yourself on the back for being an awesome contributor.
108
+ 7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
109
+
@@ -0,0 +1,110 @@
1
+ Metadata-Version: 2.1
2
+ Name: airbyte-source-okta
3
+ Version: 0.1.16
4
+ Summary: Source implementation for Okta.
5
+ Author: Airbyte
6
+ Author-email: contact@airbyte.io
7
+ Description-Content-Type: text/markdown
8
+ Requires-Dist: airbyte-cdk
9
+ Requires-Dist: pendulum==1.2.0
10
+ Provides-Extra: tests
11
+ Requires-Dist: pytest~=6.1; extra == "tests"
12
+ Requires-Dist: pytest-mock~=3.6.1; extra == "tests"
13
+ Requires-Dist: requests-mock; extra == "tests"
14
+
15
+ # Okta Source
16
+
17
+ This is the repository for the Okta source connector, written in Python.
18
+ For information about how to use this connector within Airbyte, see [the documentation](https://docs.airbyte.io/integrations/sources/okta).
19
+
20
+
21
+
22
+ **To iterate on this connector, make sure to complete this prerequisites section.**
23
+
24
+
25
+ From this connector directory, create a virtual environment:
26
+
27
+ ```shell
28
+ python -m venv .venv
29
+ ```
30
+
31
+ This will generate a virtualenv for this module in `.venv/`. Make sure this venv is active in your
32
+ development environment of choice. To activate it from the terminal, run:
33
+
34
+ ```shell
35
+ source .venv/bin/activate
36
+ pip install -r requirements.txt
37
+ ```
38
+
39
+ If you are in an IDE, follow your IDE's instructions to activate the virtualenv.
40
+
41
+ Note that while we are installing dependencies from `requirements.txt`, you should only edit `setup.py` for your dependencies. `requirements.txt` is
42
+ used for editable installs (`pip install -e`) to pull in Python dependencies from the monorepo and will call `setup.py`.
43
+ 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
44
+ should work as you expect.
45
+
46
+
47
+ **If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/okta)
48
+ to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_okta/spec.json` file.
49
+ Note that any directory named `secrets` is gitignored across the entire Airbyte repo, so there is no danger of accidentally checking in sensitive information.
50
+ See `integration_tests/sample_config.json` for a sample config file.
51
+
52
+ **If you are an Airbyte core member**, copy the credentials in Lastpass under the secret name `source okta test creds`
53
+ and place them into `secrets/config.json`.
54
+
55
+
56
+ ```shell
57
+ python main.py spec
58
+ python main.py check --config secrets/config.json
59
+ python main.py discover --config secrets/config.json
60
+ python main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.json
61
+ ```
62
+
63
+
64
+
65
+ **Via [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md) (recommended):**
66
+ ```bash
67
+ airbyte-ci connectors --name=source-okta build
68
+ ```
69
+
70
+ An image will be built with the tag `airbyte/source-okta:dev`.
71
+
72
+ **Via `docker build`:**
73
+ ```bash
74
+ docker build -t airbyte/source-okta:dev .
75
+ ```
76
+
77
+
78
+ Then run any of the connector commands as follows:
79
+
80
+ ```shell
81
+ docker run --rm airbyte/source-okta:dev spec
82
+ docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-okta:dev check --config /secrets/config.json
83
+ docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-okta:dev discover --config /secrets/config.json
84
+ docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-okta:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json
85
+ ```
86
+
87
+
88
+ You can run our full test suite locally using [`airbyte-ci`](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/pipelines/README.md):
89
+ ```bash
90
+ airbyte-ci connectors --name=source-okta test
91
+ ```
92
+
93
+ 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.
94
+ 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.
95
+
96
+
97
+ 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.
98
+ We split dependencies between two groups, dependencies that are:
99
+
100
+ * required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
101
+ * required for the testing need to go to `TEST_REQUIREMENTS` list
102
+
103
+ You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
104
+ 1. Make sure your changes are passing our test suite: `airbyte-ci connectors --name=source-okta test`
105
+ 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).
106
+ 3. Make sure the `metadata.yaml` content is up to date.
107
+ 4. Make the connector documentation and its changelog is up to date (`docs/integrations/sources/okta.md`).
108
+ 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).
109
+ 6. Pat yourself on the back for being an awesome contributor.
110
+ 7. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
@@ -0,0 +1,31 @@
1
+ README.md
2
+ setup.cfg
3
+ setup.py
4
+ airbyte_source_okta.egg-info/PKG-INFO
5
+ airbyte_source_okta.egg-info/SOURCES.txt
6
+ airbyte_source_okta.egg-info/dependency_links.txt
7
+ airbyte_source_okta.egg-info/entry_points.txt
8
+ airbyte_source_okta.egg-info/requires.txt
9
+ airbyte_source_okta.egg-info/top_level.txt
10
+ integration_tests/__init__.py
11
+ integration_tests/abnormal_state.json
12
+ integration_tests/acceptance.py
13
+ integration_tests/catalog.json
14
+ integration_tests/configured_catalog.json
15
+ integration_tests/incremental_configured_catalog.json
16
+ integration_tests/invalid_config.json
17
+ source_okta/__init__.py
18
+ source_okta/authenticator.py
19
+ source_okta/run.py
20
+ source_okta/source.py
21
+ source_okta/spec.json
22
+ source_okta/utils.py
23
+ source_okta/schemas/custom_roles.json
24
+ source_okta/schemas/group_members.json
25
+ source_okta/schemas/group_role_assignments.json
26
+ source_okta/schemas/groups.json
27
+ source_okta/schemas/logs.json
28
+ source_okta/schemas/permissions.json
29
+ source_okta/schemas/resource_sets.json
30
+ source_okta/schemas/user_role_assignments.json
31
+ source_okta/schemas/users.json
@@ -0,0 +1,2 @@
1
+ [console_scripts]
2
+ source-okta = source_okta.run:run
@@ -0,0 +1,7 @@
1
+ airbyte-cdk
2
+ pendulum==1.2.0
3
+
4
+ [tests]
5
+ pytest~=6.1
6
+ pytest-mock~=3.6.1
7
+ requests-mock
@@ -0,0 +1,2 @@
1
+ integration_tests
2
+ source_okta
@@ -0,0 +1,3 @@
1
+ #
2
+ # Copyright (c) 2023 Airbyte, Inc., all rights reserved.
3
+ #
@@ -0,0 +1,57 @@
1
+ [
2
+ {
3
+ "type": "STREAM",
4
+ "stream": {
5
+ "stream_state": {
6
+ "lastUpdated": "3021-09-08T07:04:28.000Z"
7
+ },
8
+ "stream_descriptor": {
9
+ "name": "users"
10
+ }
11
+ }
12
+ },
13
+ {
14
+ "type": "STREAM",
15
+ "stream": {
16
+ "stream_state": {
17
+ "lastUpdated": "3021-09-08T07:04:28.000Z"
18
+ },
19
+ "stream_descriptor": {
20
+ "name": "groups"
21
+ }
22
+ }
23
+ },
24
+ {
25
+ "type": "STREAM",
26
+ "stream": {
27
+ "stream_state": {
28
+ "id": "00uzzzzzzzzzzzzzzzzz"
29
+ },
30
+ "stream_descriptor": {
31
+ "name": "group_members"
32
+ }
33
+ }
34
+ },
35
+ {
36
+ "type": "STREAM",
37
+ "stream": {
38
+ "stream_state": {
39
+ "published": "3021-09-08T07:04:28.000Z"
40
+ },
41
+ "stream_descriptor": {
42
+ "name": "logs"
43
+ }
44
+ }
45
+ },
46
+ {
47
+ "type": "STREAM",
48
+ "stream": {
49
+ "stream_state": {
50
+ "id": "iamzzzzzzzzzzzzzzzzz"
51
+ },
52
+ "stream_descriptor": {
53
+ "name": "resource_sets"
54
+ }
55
+ }
56
+ }
57
+ ]
@@ -0,0 +1,15 @@
1
+ #
2
+ # Copyright (c) 2023 Airbyte, Inc., all rights reserved.
3
+ #
4
+
5
+ import pytest
6
+
7
+ pytest_plugins = ("connector_acceptance_test.plugin",)
8
+
9
+
10
+ @pytest.fixture(scope="session", autouse=True)
11
+ def connector_setup():
12
+ """This fixture is a placeholder for external resources that acceptance test might require."""
13
+ # TODO: setup test dependencies
14
+ yield
15
+ # TODO: clean up test dependencies
@@ -0,0 +1,80 @@
1
+ {
2
+ "streams": [
3
+ {
4
+ "stream": {
5
+ "name": "groups",
6
+ "json_schema": {}
7
+ },
8
+ "sync_mode": "incremental",
9
+ "destination_sync_mode": "overwrite",
10
+ "cursor_field": ["lastUpdated"],
11
+ "primary_key": [["id"]]
12
+ },
13
+ {
14
+ "stream": {
15
+ "name": "logs",
16
+ "json_schema": {}
17
+ },
18
+ "sync_mode": "incremental",
19
+ "destination_sync_mode": "overwrite",
20
+ "cursor_field": ["published"],
21
+ "primary_key": [["uuid"]]
22
+ },
23
+ {
24
+ "stream": {
25
+ "name": "users",
26
+ "json_schema": {}
27
+ },
28
+ "sync_mode": "incremental",
29
+ "destination_sync_mode": "overwrite",
30
+ "cursor_field": ["lastUpdated"],
31
+ "primary_key": [["id"]]
32
+ },
33
+ {
34
+ "stream": {
35
+ "name": "groupMembers",
36
+ "json_schema": {}
37
+ },
38
+ "sync_mode": "incremental",
39
+ "destination_sync_mode": "overwrite",
40
+ "cursor_field": ["id"],
41
+ "primary_key": [["id"]]
42
+ },
43
+ {
44
+ "stream": {
45
+ "name": "custom_roles",
46
+ "json_schema": {}
47
+ },
48
+ "sync_mode": "full_refresh",
49
+ "destination_sync_mode": "overwrite",
50
+ "primary_key": [["id"]]
51
+ },
52
+ {
53
+ "stream": {
54
+ "name": "user_role_assignments",
55
+ "json_schema": {}
56
+ },
57
+ "sync_mode": "full_refresh",
58
+ "destination_sync_mode": "overwrite",
59
+ "primary_key": [["id"]]
60
+ },
61
+ {
62
+ "stream": {
63
+ "name": "group_role_assignments",
64
+ "json_schema": {}
65
+ },
66
+ "sync_mode": "full_refresh",
67
+ "destination_sync_mode": "overwrite",
68
+ "primary_key": [["id"]]
69
+ },
70
+ {
71
+ "stream": {
72
+ "name": "permissions",
73
+ "json_schema": {}
74
+ },
75
+ "sync_mode": "full_refresh",
76
+ "destination_sync_mode": "overwrite",
77
+ "primary_key": [["label"]]
78
+ }
79
+ ]
80
+ }
@@ -0,0 +1,96 @@
1
+ {
2
+ "streams": [
3
+ {
4
+ "stream": {
5
+ "name": "users",
6
+ "json_schema": {},
7
+ "supported_sync_modes": ["full_refresh", "incremental"]
8
+ },
9
+ "sync_mode": "incremental",
10
+ "destination_sync_mode": "overwrite",
11
+ "cursor_field": ["lastUpdated"],
12
+ "primary_key": [["id"]]
13
+ },
14
+ {
15
+ "stream": {
16
+ "name": "groups",
17
+ "json_schema": {},
18
+ "supported_sync_modes": ["full_refresh", "incremental"]
19
+ },
20
+ "sync_mode": "incremental",
21
+ "destination_sync_mode": "overwrite",
22
+ "cursor_field": ["lastUpdated"],
23
+ "primary_key": [["id"]]
24
+ },
25
+ {
26
+ "stream": {
27
+ "name": "group_members",
28
+ "json_schema": {},
29
+ "supported_sync_modes": ["full_refresh", "incremental"]
30
+ },
31
+ "sync_mode": "incremental",
32
+ "destination_sync_mode": "overwrite",
33
+ "cursor_field": ["id"],
34
+ "primary_key": [["id"]]
35
+ },
36
+ {
37
+ "stream": {
38
+ "name": "resource_sets",
39
+ "json_schema": {},
40
+ "supported_sync_modes": ["full_refresh", "incremental"]
41
+ },
42
+ "sync_mode": "incremental",
43
+ "destination_sync_mode": "overwrite",
44
+ "cursor_field": ["id"],
45
+ "primary_key": [["id"]]
46
+ },
47
+ {
48
+ "stream": {
49
+ "name": "custom_roles",
50
+ "json_schema": {},
51
+ "supported_sync_modes": ["full_refresh"]
52
+ },
53
+ "sync_mode": "full_refresh",
54
+ "destination_sync_mode": "overwrite"
55
+ },
56
+ {
57
+ "stream": {
58
+ "name": "user_role_assignments",
59
+ "json_schema": {},
60
+ "supported_sync_modes": ["full_refresh"]
61
+ },
62
+ "sync_mode": "full_refresh",
63
+ "destination_sync_mode": "overwrite"
64
+ },
65
+ {
66
+ "stream": {
67
+ "name": "group_role_assignments",
68
+ "json_schema": {},
69
+ "supported_sync_modes": ["full_refresh"]
70
+ },
71
+ "sync_mode": "full_refresh",
72
+ "destination_sync_mode": "overwrite"
73
+ },
74
+ {
75
+ "stream": {
76
+ "name": "permissions",
77
+ "json_schema": {},
78
+ "supported_sync_modes": ["full_refresh"]
79
+ },
80
+ "sync_mode": "full_refresh",
81
+ "destination_sync_mode": "overwrite",
82
+ "primary_key": [["label"]]
83
+ },
84
+ {
85
+ "stream": {
86
+ "name": "logs",
87
+ "json_schema": {},
88
+ "supported_sync_modes": ["full_refresh", "incremental"]
89
+ },
90
+ "sync_mode": "incremental",
91
+ "destination_sync_mode": "overwrite",
92
+ "cursor_field": ["published"],
93
+ "primary_key": [["uuid"]]
94
+ }
95
+ ]
96
+ }
@@ -0,0 +1,37 @@
1
+ {
2
+ "streams": [
3
+ {
4
+ "stream": {
5
+ "name": "users",
6
+ "json_schema": {},
7
+ "supported_sync_modes": ["full_refresh", "incremental"]
8
+ },
9
+ "sync_mode": "incremental",
10
+ "destination_sync_mode": "overwrite",
11
+ "cursor_field": ["lastUpdated"],
12
+ "primary_key": [["id"]]
13
+ },
14
+ {
15
+ "stream": {
16
+ "name": "groups",
17
+ "json_schema": {},
18
+ "supported_sync_modes": ["full_refresh", "incremental"]
19
+ },
20
+ "sync_mode": "incremental",
21
+ "destination_sync_mode": "overwrite",
22
+ "cursor_field": ["lastUpdated"],
23
+ "primary_key": [["id"]]
24
+ },
25
+ {
26
+ "stream": {
27
+ "name": "logs",
28
+ "json_schema": {},
29
+ "supported_sync_modes": ["full_refresh", "incremental"]
30
+ },
31
+ "sync_mode": "incremental",
32
+ "destination_sync_mode": "overwrite",
33
+ "cursor_field": ["published"],
34
+ "primary_key": [["uuid"]]
35
+ }
36
+ ]
37
+ }