Skip to content

feat(agent): richer deploy output with deployment name and links - #933

Merged
JackNDwyer merged 1 commit into
mainfrom
jack/devx-641/deploy-output-links
Aug 6, 2026
Merged

feat(agent): richer deploy output with deployment name and links#933
JackNDwyer merged 1 commit into
mainfrom
jack/devx-641/deploy-output-links

Conversation

@JackNDwyer

Copy link
Copy Markdown
Contributor

Context

Part of the agent deployments beta polish (DEVX-641). Beta feedback (Ben): the end of lk agent deploy just prints Deployed agent with no indication of which deployment/version went live or where to go next. This makes the output actionable.

Changes

After a successful lk agent deploy, print:

Completed deployment of agent <name> to <deployment> (<version>)
View analytics: <link>
Test in Agent Console: <link>
  • <deployment> is production when --deployment is omitted, else the deployment name.
  • Agent name and live version are resolved with a single existing ListAgents call. If that lookup fails, output falls back to the minimal summary (Completed deployment of agent to <deployment>) — a successful deploy is never reported as an error.
  • The Test in Agent Console link is deep-linked to the deployment via a new deployment query param on cloudConsoleURL.
  • New cloudAgentURL helper builds the analytics (agent detail) link.
  • Links are omitted for non-cloud projects (self-hosted / localhost), matching lk agent start.

Tests

  • Extended TestCloudConsoleURL with deployment-param cases (including query-escaping).
  • Added TestCloudAgentURL.
  • go build, go vet, gofmt, and go test ./cmd/lk/ all clean.

Related: livekit/web#5406 (Console deployment badge), livekit/web#4660 (docs).

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@JackNDwyer
JackNDwyer force-pushed the jack/devx-641/deploy-output-links branch from 3229209 to e0ed2c6 Compare August 5, 2026 23:30
After a successful `lk agent deploy`, report the agent name, target
deployment, and links to the agent details page and the agent console
(deep-linked to the deployment). Name comes from the agent-level
ListAgents field, which is ready at deploy time (the per-region field
isn't populated until the agent is scraped). Falls back to a minimal
status line if the lookup fails.

Version is intentionally omitted: no source is both correct and ready
synchronously at deploy time (the deploy API doesn't return it, the
agent-level version is production-only, and the per-deployment version
isn't scraped yet).

Console deep-link carries the deployment as a query param.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@JackNDwyer
JackNDwyer force-pushed the jack/devx-641/deploy-output-links branch from e0ed2c6 to d401f00 Compare August 6, 2026 13:55

@yoonsio yoonsio left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@JackNDwyer
JackNDwyer merged commit e335a98 into main Aug 6, 2026
21 of 22 checks passed
@JackNDwyer
JackNDwyer deleted the jack/devx-641/deploy-output-links branch August 6, 2026 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants