feat: add unified lifecycle wait support#14
Merged
Conversation
Collaborator
|
Great for script orchestration, thanks! Does tdc fs create-file-system need this optional flag as well? |
guangleibao
approved these changes
Jul 18, 2026
Icemap
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Add a consistent optional
--waitflag to asynchronous Starter DB and TiDB Cloud Filesystem lifecycle commands while preserving their existing non-blocking default behavior.--waitcompletion conditiontdc db create-db-clusterACTIVEtdc db create-db-cluster-branchACTIVEtdc db delete-db-clusterDELETEDor is no longer accessible after the accepted deletiontdc fs create-file-systemWait failures never delete or recreate accepted resources. Errors identify the affected resource and explain whether creation remains allocated or deletion may still be in progress. Filesystem deletion remains asynchronous because Drive9 does not expose a reliable remote deletion-completion API; its successful output now correctly reports
deletinginstead ofdeleted.Update the repository README Agent's Toolbelt stories, completed lifecycle specs, AGENTS guidance, and presentation material to use the unified flag. Matching English and Chinese user-documentation updates remain in their own repositories and are intentionally not pinned to fork-only commits by this PR. Live e2e lifecycle orchestration now uses the product-level wait flags instead of duplicating create/delete polling in test code.
Verification
go test ./...make e2emake live-e2e-dbmake live-e2e-fsdeletingoutput validation