fix: wait for quota state after creation #385
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.
We are using this provider to maintain kafka resources, including quotas.
When creating and updating quotas is fails in 90% of cases because the provider creates it in kafka, and then immediately queries for it, but it doesn't find it at this point, as it seems it takes a little bit of time to appear in Kafka.
Here are the logs we were getting for such a scenario:
With this fix, we'll be waiting until the quota is created in Kafka (just like for topics).
I tested this locally and it fixes the issue.