chore: Introduce opt-in flag to enable persistence support #250
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The SDK test harness has historically been self-sufficient. With the introduction of persistence-based unit tests, that is no longer the case. Externally started services are required for each persistence technology supported.
Since we want to retain the ease of use associated with a our current
go run .
usage, we are going to disable persistence support by default. Users will have to provide a-enable-persistence-tests
if they want the test harness to attempt those tests.SDKs under test are still required to provide the appropriate capabilities. In the event those capabilities are provided, but the test harness flag is not provided, persistence tests will be skipped.