Tags: bitalizer/cli
Tags
`temporal worker deployment create|create-version` (temporalio#971) Adds implementation of the `temporal worker deployment create` and `temporal worker deployment create-version` CLI commands using only direct gRPC API calls, not the sdk-go client code. Adds some basic unit tests for both commands though due to the server-side validation of proper AWS IAM credentials, the happy-path `temporal worker deployment create-version` call with AWS Lambda compute config is skipped until such time as we can figure out adding real AWS test fixtures. --------- Signed-off-by: Jay Pipes <jay.pipes@temporal.io> Co-authored-by: Alex Stanfield <13949480+chaptersix@users.noreply.github.com> Co-authored-by: Dan Davison <dan.davison@temporal.io> Co-authored-by: Sean Kane <spkane31@gmail.com> Co-authored-by: Tasha Alfano <tashalalfano@gmail.com> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
update dev server to 1.30.2 and go to 1.26.1 (temporalio#967) ## Summary - Bump `go.temporal.io/server` from v1.30.1 to v1.30.2 - Bump Go from 1.26.0 to 1.26.1, fixing 5 stdlib vulnerabilities (GO-2026-4599 through GO-2026-4603) - Fix flaky `TestDeployment_Describe_Version_TaskQueueStats_WithPriority` test: relax rate assertion that assumed task rates < 1, but server can return rates > 1 ## Test plan - [ ] CI passes - [ ] govulncheck reports no symbol-level vulnerabilities
bump server version to 151.6 (temporalio#961)
SAA drop type and task queue (temporalio#959) ## What was changed Drop execution type and task queue from start standalone activity output ## Why? They are not currently guaranteed correct in the `conflictPolicy=UseExisting` case ## Testing ``` $ temporal activity start --start-to-close-timeout 1s --task-queue hello-standalone-activity-task-queue --type compose_greeting --activity-id act-1 --input '{"greeting": "mygreeting", "name": "myname"}' Running execution: ActivityId act-1 RunId 019cd407-83cc-7c8e-ba17-5a3125e4e7cd Namespace default $ temporal activity result -a act-1 Results: Status COMPLETED Result "mygreeting, myname!" $ temporal activity start --start-to-close-timeout 1s --task-queue hello-standalone-activity-task-queue --type compose_greeting --activity-id act-2 -o json --input '{"greeting": "mygreeting", "name": "myname"}' { "activityId": "act-2", "runId": "019cd408-38a3-7e15-8b36-58f966f156de", "namespace": "default" } ```
Bump server to v1.31.0-151.0 (temporalio#946) For an unstable release to be used in SDK testing. Note the base branch.
Implement ListWorkers and DescribeWorker (temporalio#867) ## What was changed <!-- Describe what has changed in this PR --> Implemented the ListWorkers and DescribeWorker gRPC requests note: list workers doesn't display all heartbeat information. Open to feedback on if we should display more/all/less fields. See screenshots in testing section for an example. PageSize is also not supported in server for the ListWorkers call, so that was left out. Added a `limit` field to allow users to limit how many results are displayed, similar to other CLI commands. Sample output of the two new commands <img width="1521" height="460" alt="image" src="/sitelet?url=https%3A%2F%2Fgithub.com%2Fbitalizer%2Fcli%2F%253Ca%2520href%3D"/sitelet?url=https%3A%2F%2Fgithub.com%2Fuser-attachments%2Fassets%2F5a45be14-1071-4e03-a7cc-e26e4d61dbc9">https://github.com/user-attachments/assets/5a45be14-1071-4e03-a7cc-e26e4d61dbc9" /> ## Why? <!-- Tell your future self why have you made these changes --> New feature. ## Checklist <!--- add/delete as needed ---> 1. Closes temporalio#868 2. How was this tested: <!--- Please describe how you tested your changes/how we can test them --> Added tests, because Go SDK doesn't support worker heartbeating yet, we manually send a `RecordWorkerHeartbeatRequest` gRPC request to mimic the behavior of a worker. 3. Any docs updates needed? <!--- update README if applicable or point out where to update docs.temporal.io -->
PreviousNext