You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Source Okta: add permission stream under a custom role (#14739)
* Source Okta: add permission stream under a custom role
- it supports full refresh only
- add unit tests
* bump connector version
* bump connector version in Dockerfile
* auto-bump connector version [ci skip]
Co-authored-by: sajarin <[email protected]>
Co-authored-by: Octavia Squidington III <[email protected]>
**If you are a community contributor**, follow the instructions in the [documentation](https://docs.airbyte.io/integrations/sources/okta)
40
48
to generate the necessary credentials. Then create a file `secrets/config.json` conforming to the `source_okta/spec.json` file.
41
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.
@@ -45,7 +53,8 @@ See `integration_tests/sample_config.json` for a sample config file.
Make sure to familiarize yourself with [pytest test discovery](https://docs.pytest.org/en/latest/goodpractices.html#test-discovery) to know how your test files and methods should be named.
80
97
First install test dependencies into your virtual environment:
81
-
```
98
+
99
+
```shell
82
100
pip install .[tests]
83
101
```
102
+
84
103
### Unit Tests
104
+
85
105
To run unit tests locally, from the connector directory run:
86
-
```
106
+
107
+
```shell
87
108
python -m pytest unit_tests
88
109
```
89
110
90
111
### Integration Tests
112
+
91
113
There are two types of integration tests: Acceptance Tests (Airbyte's test suite for all source connectors) and custom integration tests (which are specific to this connector).
114
+
92
115
#### Custom Integration tests
93
-
Place custom tests inside `integration_tests/` folder, then, from the connector root, run
116
+
117
+
Place custom tests inside the `integration_tests``/` folder, then, from the connector root, run
118
+
94
119
```
95
120
python -m pytest integration_tests
96
121
```
122
+
97
123
#### Acceptance Tests
124
+
98
125
Customize `acceptance-test-config.yml` file to configure tests. See [Source Acceptance Tests](https://docs.airbyte.io/connector-development/testing-connectors/source-acceptance-tests-reference) for more information.
99
126
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.
100
127
To run your integration tests with acceptance tests, from the connector root, run
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.
120
154
We split dependencies between two groups, dependencies that are:
155
+
121
156
* required for your connector to work need to go to `MAIN_REQUIREMENTS` list.
122
157
* required for the testing need to go to `TEST_REQUIREMENTS` list
123
158
124
159
### Publishing a new version of the connector
160
+
125
161
You've checked out the repo, implemented a million dollar feature, and you're ready to share your changes with the world. Now what?
162
+
126
163
1. Make sure your changes are passing unit and integration tests.
127
-
1. Bump the connector version in `Dockerfile` -- just increment the value of the `LABEL io.airbyte.version` appropriately (we use [SemVer](https://semver.org/)).
128
-
1. Create a Pull Request.
129
-
1. Pat yourself on the back for being an awesome contributor.
130
-
1. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
164
+
2. Bump the connector version in `Dockerfile` -- just increment the value of the `LABEL io.airbyte.version` appropriately (we use [SemVer](https://semver.org/)).
165
+
3. Create a Pull Request.
166
+
4. Pat yourself on the back for being an awesome contributor.
167
+
5. Someone from Airbyte will take a look at your PR and iterate with you to merge it into master.
0 commit comments