Skip to content

Replace references to tctl with Temporal CLI #260

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yuandrew merged 1 commit into from
Oct 20, 2025
Merged

Replace references to tctl with Temporal CLI #260

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions resource_pool/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ You should see output indicating that the `ResourcePoolWorkflow` serialized acce

You can query the set of current resource resource holders with:

tctl wf query -w resource_pool --qt get_current_holders
temporal workflow query --workflow-id resource_pool --name get_current_holders

# Other approaches

Expand All @@ -41,7 +41,7 @@ Temporal's durable execution guarantees, this can only happen if:

If a leak were to happen, you could discover the identity of the leaker using the query above, then:

tctl wf signal -w resource_pool --name release_resource --input '{ "release_key": "<the key from the query above>" }
temporal workflow signal --workflow-id resource_pool --name release_resource --input '{ "release_key": "<the key from the query above>" }'

Performance: A single ResourcePoolWorkflow scales to tens, but not hundreds, of request/release events per second. It is
best suited for allocating resources to long-running workflows. Actual performance will depend on your temporal server's
Expand Down
Loading