Skip to content

Conversation

@cd-work
Copy link
Contributor

@cd-work cd-work commented Dec 9, 2024

This patch adds the new phylum firewall log to allow checking the Aviary log from the CLI.

While the UI gives a more user-friendly overview, this should be complementary by giving access to the data in a structure closer to the original layout.

The CLI arguments allow applying most filters exposed by the API, but combine the individual package components into a PURL to avoid an excessive number of arguments.

Currently neither the --json output nor the pretty-printer have a way to paginate through the logs. While this could be done either automatically or by manually specifying the pagination offset, it seems to me like the limit of 10_000 entries per page should be sufficient for all current usecases.

Contrary to our existing timestamp columns, the timestamp in the output table uses nanosecond precision. The additional precision seems worthwhile in this case since this automatically groups versions together if they were submitted for analysis as a batch.

tmp

@cd-work cd-work requested a review from a team as a code owner December 9, 2024 08:34
@cd-work cd-work requested a review from mathew-horner December 9, 2024 08:34
@cd-work cd-work force-pushed the aviary_logs branch 2 times, most recently from 2eedf40 to 4f5f4fa Compare December 9, 2024 08:41
This patch adds the new `phylum firewall log` to allow checking the
Aviary log from the CLI.

While the UI gives a more user-friendly overview, this should be
complementary by giving access to the data in a structure closer to the
original layout.

The CLI arguments allow applying most filters exposed by the API, but
combine the individual package components into a PURL to avoid an
excessive number of arguments.

Currently neither the `--json` output nor the pretty-printer have a way
to paginate through the logs. While this could be done either
automatically or by manually specifying the pagination offset, it seems
to me like the limit of 10_000 entries per page should be sufficient for
all current usecases.

Contrary to our existing timestamp columns, the timestamp in the output
table uses nanosecond precision. The additional precision seems
worthwhile in this case since this automatically groups versions
together if they were submitted for analysis as a batch.
@cd-work cd-work requested a review from maxrake December 10, 2024 17:29
Copy link
Contributor

@maxrake maxrake left a comment

Choose a reason for hiding this comment

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

LGTM

@cd-work cd-work merged commit 0341dd8 into main Dec 10, 2024
17 checks passed
@cd-work cd-work deleted the aviary_logs branch December 10, 2024 18:03
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