• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

astronomer / astro-cli / 39464190922
61%
main: 45%

Build:
Build:
LAST BUILD BRANCH: apc-deployment-name
DEFAULT BRANCH: main
Ran 20 Oct 2026 05:17PM UTC
Jobs 1
Files 346
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

20 Oct 2026 05:13PM UTC coverage: 60.534% (+0.06%) from 60.474%
39464190922

push

github

web-flow
Give --workspace only to the deployment commands that read it (#2391)

* Give --workspace only to the deployment commands that read it

astro deployment registered --workspace (and 1.x's --workspace-id) on the
whole group, so team, user and most token commands showed a flag they never
read, and passing it still made followProject skip the project's workspace
and host. It is now on the commands that read it: list, create (and
--clone), update, delete, logs, inspect, hibernate, wake-up, the variable,
worker-queue and bundle commands, and token workspace-token add and remove.
The rest keep 1.x's --workspace-id, hidden and read by nothing, which
chooses no workspace.

On APC the group's --workspace-id moves to create, list and adopt. The
other commands 1.x had keep it as a hidden no-op; hibernate and wake-up,
newer than 1.x, take none.

Bugs fixed on the way:
- deployment list --all, on both platforms, found the workspace before
  reading --all, so it failed with no workspace to find (an org token).
- APC's coalesceWorkspace read the context before --workspace-id, so a
  context with no workspace failed a command that named one.
- token workspace-token add and remove read the raw flag, so the
  project's workspace was ignored; they go through coalesceWorkspace.
- workspace team list takes --workspace like its siblings, and it and
  workspace user list show the role on the current workspace, which they
  compared with "" and left blank.

Co-Authored-By: Claude <noreply@anthropic.com>

* Say what replaced --workspace on deployment team, user and token

They took a --workspace in v2 until the previous commit, and now answer it
with cobra's bare "unknown flag". A v2Only removed-flag entry tells such a
run that these commands act on the Deployment it names, which carries its
workspace; 1.x's --workspace-id stays a no-op, workspace-token add and
remove still take --workspace, and APC's commands of these names, which
never had one, keep cobra's error.

Also pin ... (continued)

83 of 105 new or added lines in 11 files covered. (79.05%)

3 existing lines in 1 file now uncovered.

41376 of 68352 relevant lines covered (60.53%)

399.32 hits per line

Uncovered Changes

Lines Coverage ∆ File
14
76.55
-0.07% internal/platform/astro/team/team.go
8
78.14
-1.29% internal/platform/astro/user/user.go

Coverage Regressions

Lines Coverage ∆ File
3
76.55
-0.07% internal/platform/astro/team/team.go
Jobs
ID Job ID Ran Files Coverage
1 39464190922.1 20 Oct 2026 05:17PM UTC 346
60.53
GitHub Action Run
Source Files on build 39464190922
  • Tree
  • List 346
  • Changed 12
  • Source Changed 12
  • Coverage Changed 12
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #39464190922
  • e8d9912f on github
  • Prev Build on v2 (#39447145560)
  • Next Build on v2 (#39481623392)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc