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

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

Build:
Build:
LAST BUILD BRANCH: v2-runtime-package-group
DEFAULT BRANCH: main
Ran 20 Oct 2026 03:22PM 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 03:18PM UTC coverage: 60.474% (+0.09%) from 60.381%
39447145560

push

github

web-flow
Read -d on astro af and astro api airflow as a link, a Deployment id, or a Deployment name (#2387)

* Read astro af -d as an id or a name when no link has it

A -d value no link declares was always sent to GET by id, so a Deployment
name 404'd. It now reads the way --deployment reads on astro deployment and
astro deploy: a link name is the link, a Deployment id (util.IsCUID) is that
Deployment, fetched across the organization with no extra call, and anything
else is a Deployment name, looked up in --workspace, else the project's
[tool.astro] workspace, else the workspace of the login the project's links
use. None, or several (listed by id), is an error; inside a project a name
that matched nothing leads with the project's links, the likelier typo.

astro af gains --workspace (v2 spelling only: af did not exist in 1.x) so a
name can be looked up outside the default workspace. With an id it has to
contain the Deployment, checked off the lookup the address needs anyway; with
a link it has to agree with the link's workspace; it cannot apply to an MWAA,
Composer or url link, nor be combined with --url, nor be empty.

The name lookup lives in internal/instancelocate, which already does the af
Deployment lookup: NamedDeployment and DeploymentNameError are exported so
astro api airflow (which imports the package) can share them, and the
locator implements a new optional DeploymentFinder seam that cmd/local asks
for. No pkg/* sub-module changes.

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

* Pin --workspace on an id end to end, paging, and apc links

Review follow-ups for astro af -d by name:

- a Deployment id given with --workspace is refused end to end when it is in
  another workspace, pinning that findDeployment carries the flag for ids as
  well as names;
- the name lookup reads every page of a workspace's listing, and a name
  shared across pages is ambiguous;
- an apc link is held to --workspace like an Astro link (its own Houston
  workspace), not... (continued)

203 of 236 new or added lines in 6 files covered. (86.02%)

41294 of 68284 relevant lines covered (60.47%)

394.2 hits per line

Uncovered Changes

Lines Coverage ∆ File
17
82.11
internal/instancelocate/deploymentname.go
9
86.42
6.11% cmd/api/airflowtarget.go
4
92.41
-0.45% cmd/local/resolve.go
2
87.29
2.47% internal/instancelocate/astro.go
1
47.54
-0.79% internal/instancelocate/instancelocate.go
Jobs
ID Job ID Ran Files Coverage
1 39447145560.1 20 Oct 2026 03:22PM UTC 346
60.47
GitHub Action Run
Source Files on build 39447145560
  • Tree
  • List 346
  • Changed 5
  • Source Changed 5
  • Coverage Changed 5
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #39447145560
  • d46b4b77 on github
  • Prev Build on v2 (#39360245809)
  • Next Build on v2 (#39464190922)
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