[ECP-9580] Fix missing idempotencyExtraData key issue in capture requests #2839
Conversation
This file contains 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
candemiralp
had a problem deploying
to
internal
GitHub Actions
Failure
candemiralp
changed the title
|
candemiralp
changed the title
khushboo-singhvi
approved these changes
Dec 30, 2024
acampos1916
approved these changes
Dec 30, 2024
Merged
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.
Description
The
idempotencyExtraDatais now set on the request builder and consumed from the correct object in the HTTP client. Previously, missing theidempotencyExtraDatakey in multiple capture request headers caused an array key not found exception.Tested scenarios