Add wait_for_database helper function to poll for Knowledge Base database creation #1
+418
−2
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.
Overview
This PR adds a
wait_for_database()
helper function to simplify polling for Knowledge Base database status during creation. Previously, users had to manually write polling loops to wait for the database to become ready, which was error-prone and required handling multiple edge cases.Problem
When creating a Knowledge Base, the database deployment can take several minutes. Users previously had to write manual polling loops like:
This approach has several issues:
Solution
Added a
wait_for_database()
helper method that:ONLINE
DECOMMISSIONED
,UNHEALTHY
) with a customKnowledgeBaseDatabaseError
APITimeoutError
if the database doesn't become ready within the timeoutUsage
Async Usage
Changes
KnowledgeBasesResource.wait_for_database()
(synchronous)AsyncKnowledgeBasesResource.wait_for_database()
(asynchronous)KnowledgeBaseDatabaseError
for failed database statesAPI Reference
Parameters:
uuid
- Knowledge base UUID to poll (required)timeout
- Maximum wait time in seconds (default: 600)poll_interval
- Time between status checks in seconds (default: 5)Returns:
KnowledgeBaseRetrieveResponse
when database status isONLINE
Raises:
KnowledgeBaseDatabaseError
- Database entered a failed state (DECOMMISSIONED
orUNHEALTHY
)APITimeoutError
- Timeout exceeded before database becameONLINE
ValueError
- Invalid UUID parameterTesting
All tests pass successfully:
Tests cover:
Backward Compatibility
✅ No breaking changes - this is a purely additive feature. Existing code continues to work unchanged, and the new helper is opt-in.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.