Skip to content

Route env set/delete through deployment service for post-deploy UX#630

Merged
phinze merged 1 commit intomainfrom
phinze/mir-701-miren-env-set-should-watch-deploy-and-print-routes-like
Feb 25, 2026
Merged

Route env set/delete through deployment service for post-deploy UX#630
phinze merged 1 commit intomainfrom
phinze/mir-701-miren-env-set-should-watch-deploy-and-print-routes-like

Conversation

@phinze
Copy link
Copy Markdown
Contributor

@phinze phinze commented Feb 23, 2026

Summary

env set and env delete were the odd ones out — they'd create a new version and bail, while deploy and rollback both watch activation and print routes. Now they all behave the same way.

  • Added SetEnvVars and DeleteEnvVars RPCs to the deployment service
  • Extracted shared env var mutation logic into api/app/envvar.go
  • CLI now gets back deployment records, polls for activation, and shows routes
  • Old Crud interface still works (thin wrappers over the shared helper)

Closes MIR-701

`miren env set` and `env delete` would create a new version and exit
immediately — no deployment record, no activation polling, no route
display. Meanwhile `deploy` and `rollback` both do all of that.

Added SetEnvVars/DeleteEnvVars RPCs to the deployment service so the CLI
can get back a deployment record + access info. Extracted the shared env
var mutation logic into api/app/envvar.go so both the deployment server
(new methods) and the app server (old Crud methods) use the same code.
@phinze phinze requested a review from a team as a code owner February 23, 2026 13:00
@phinze phinze merged commit a217814 into main Feb 25, 2026
9 checks passed
@phinze phinze deleted the phinze/mir-701-miren-env-set-should-watch-deploy-and-print-routes-like branch February 25, 2026 13:33
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.

2 participants