improve Azure SDK VCR replay handling and polling behavior#1312
Open
improve Azure SDK VCR replay handling and polling behavior#1312
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Community Note
Description
Refines current vcr integration and simplify some of the vcr logic. These changes make VCR replay handling more explicit, improve replay-with-new-episodes behavior, and ensure replay misses surface immediately instead of going through normal retry/backoff paths.
Detailed AI generated implementation summary Gist Link
The existing integration already supported skipping polling delay, but replay mode detection still depended on complex reflection and replay misses could be misclassified as retryable failures. That could lead to unnecessary waits or stuck tests when a cassette interaction was missing.
Testing
handling, and polling behavior changes
trigger an interaction not found error
Please find attached test logs from the local validation runs
This is a (please select all that apply):
Related Issue(s)
Fixes #0000
Rollback Plan
If a change needs to be reverted, we will publish an updated version of the provider.
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
Note
If this PR changes meaningfully during the course of review please update the title and description as required.