Bugfix/admin timeouts #342
Merged
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.
Added timeout arguments across all REST API calls and provided a way to set them from the
Application
level.There are 2 options,
request_timeout
andtopic_create_timeout
(which is more of a wait/validation step vs actual request timeout).lowest level API defaults were kept where possible (ex if Confluent Kafka AdminClient
list_topics
has -1 timeout, ourTopicAdmin
uses that as default for it'slist_topics
), but for the most part those defaults are overridden by a parent class (ex.TopicAdmin
will always receivetimeout
arguments fromTopicManager
, which is ultimately set by theApplication
class setting.in terms of tests, made sure that if one API call called another that the corresponding
timeout
was passed down correctly. Most of the additions are just making suretimeout
was actually included in the arguments.