[CRE-1041] More robust check if error is retryable for Red Panda's schema registration #2185
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.
Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.
Why
The changes improve error handling and retry logic for schema registration and existence checks with the Red Panda schema registry. By closing response bodies properly before retries and enhancing the determination of retryable errors, these updates aim to make the schema registration process more robust against transient network and HTTP errors.
What
framework/components/dockercompose/.changeset/v0.1.15.md
framework/components/dockercompose/chip_ingress_set/protos.go
checkSchemaExists
andregisterSingleProto
functions, preventing resource leaks.isRetryableError
function to include a broader range of network and HTTP errors for retries, such as timeouts and connection resets, making error handling more comprehensive.