Skip to content

Commit cfdd389

Browse files
committed
Update README to clarify harness mode functionality and its impact on deprecated endpoints.
1 parent 2d647d6 commit cfdd389

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Full documentation on this Python wrapper is available in [this link](https://he
88

99
## Using in Harness Mode
1010

11-
Starting with version 3.5.0, the Split API client supports operating in "harness mode" to interact with both Split and Harness APIs. This is required for usage in environments that have been migrated to Harness and want to use the new features.
11+
Starting with version 3.5.0, the Split API client supports operating in "harness mode" to interact with both Split and Harness APIs. This is required for usage in environments that have been migrated to Harness **and** want to use the new features. Operating not in harness mode will work as it did before with existing Split bearer tokens, but the deprecated endpoints mentioned below will not function.
1212

1313
For detailed information about Harness API endpoints, please refer to the [official Harness API documentation](https://apidocs.harness.io/).
1414

0 commit comments

Comments
 (0)