astronomer / astro-cli / 39833131442

61%

main: 45%

push

github

Shape APC's astro deployment logs as Astro's: one command, flags pick the components (#2417)

* Shape APC's astro deployment logs as Astro's: one command, flags pick the components

astro deployment logs [DEPLOYMENT_ID] on APC now runs itself, as Astro's
does: every component's logs, merged oldest first, unless --webserver,
--scheduler, --workers, --triggerer (where the platform runs one) or
--component pick some. Houston answers for one component per request, so
the CLI asks once for each and merges the answers by time; several
components in text each end with their component, as Astro's end with
their source, and -o json names it on every record as before.

--follow streams one component, as Houston's subscription does, and is
refused with none or several picked. --since and --follow stay APC's own.

1.x's astro deployment logs <component> <ID> still runs as it did, with
--search, hidden from help. The triggerer subcommand, new in v2, gives way
to --triggerer.

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

* Test that --component skips the empty names a stray comma leaves

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

* Keep one component's logs in Houston's order, and refuse a component where the Deployment goes

From review. deployment.Logs merges by time only when it merges several
components and Houston gave every record a time it can read; one
component's records, as the hidden 1.x subcommands show them, keep
Houston's order, and several with an unreadable time are left one
component after another rather than ordered by a guess. It returns
houston.DeploymentLog with Component set to the one asked for, in place of
a wrapper that shadowed that field.

astro deployment logs triggerer <ID>, an earlier v2's layout, took
"triggerer" for a Deployment id; a component where the Deployment goes is
now a usage error naming its flag. An unknown --component is quoted as
typed, and the list it gives names workers too.

Co-Authored-By: Claude <noreply@ant... (continued)

130 of 132 new or added lines in 3 files covered. (98.48%)

41635 of 68648 relevant lines covered (60.65%)

409.99 hits per line