feat(mads) allow specifying fetch-timeout via query param #2148
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.
Summary
Follow up on #2121, adds a query parameter (
fetch-timeout
) to allow clients to specify how long a single HTTP long polling request should wait.Originally was thinking a GRPC TimeoutValue and TimeoutUnit made sense as the format, but we use golang's
time.Duration
format elsewhere in the config, and a parser already exists for it, so went with that instead.If the timeout value is less than or equal to 0, the request does a sync fetch instead.
Full changelog
fetch-timeout
query parameter to the MADS V1 HTTP endpointDocumentation
Testing