Skip to content

cloud-agents environment support#816

Open
yoonsio wants to merge 2 commits intomainfrom
sy/env
Open

cloud-agents environment support#816
yoonsio wants to merge 2 commits intomainfrom
sy/env

Conversation

@yoonsio
Copy link
Copy Markdown
Contributor

@yoonsio yoonsio commented Apr 7, 2026

Adds --env flag to create, destroy and update-secrets commands.

  • create/deploy: environment defaults to production.
  • update-secrets: can associate secrets with multiple environments.
  • secrets: show environments column in agent secrets table.

TODO: remove replace directive in go.mod once protocol changes are merged.

ref AP-638

@yoonsio yoonsio requested a review from a team April 7, 2026 17:19
Comment thread go.mod
sigs.k8s.io/json v0.0.0-20241014173422-cfa47c3a1cc8 // indirect
)

replace github.com/livekit/server-sdk-go/v2 => /Users/syoon/src/server-sdk-go
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.

saw your note, just another reminder

Comment thread go.mod
k8s.io/apimachinery v0.34.1
)

replace github.com/livekit/protocol => /Users/syoon/src/protocol
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.

same here

Copy link
Copy Markdown
Contributor

@real-danm real-danm left a comment

Choose a reason for hiding this comment

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

lgtm, will the block a release until server side is ready? have to coordinate the rollout if so

Comment thread cmd/lk/agent.go
Name: "env",
Usage: "Deployment environment(s). For create/deploy, specifies the target environment (defaults to 'production'). For update-secrets, assigns environment(s) to the secret. Can be specified multiple times (e.g. --env staging --env production).",
Required: false,
}
Copy link
Copy Markdown

@shawnyang-coder shawnyang-coder Apr 14, 2026

Choose a reason for hiding this comment

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

Why only create/deploy/update-secrets? What about other rpc like status/update?

Can an agent (identified by unique agent_id) be in both Staging and Prod ? or only one env at any time?

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