Shared recordings 1: exposing recording_id
in Rust SDK
#4383
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.
We already exposed a way of configuring the
StoreId
, but this is an internal concept that we have never communicated anywhere and is very likely to be unstable as the way we do blueprint recordings evolve (also it's been known to confuse users).This adds a simple, straightforward way of configuring the
recording_id
, akin to what we have in the Python SDK.Part of a PR series to fix #4055 once and for all:
recording_id
in Rust SDK #4383recording_id
in C and C++ SDKs #4384Checklist