Closed chelma closed 8 months ago
Some initial thoughts as I think through the user experience here. There's a lot of ways to structure this so I'll start with making a list of actions that a user might want to perform.
Additionally, we'll want a way to specify whether we're looking for/listing Capture config or Viewer config.
Whoops, didn't mean to close the ticket
Some additional thoughts:
After some thought, I think I'll start with the following experience:
config-list --capture
and config-list --viewer
. This maintains congruence with our existing config-update
command, which itself can be expanded to use the same nomenclature to update JUST the capture or viewer config at a later date.--capture
/--viewer
flag is a required argument. This could be an indication that we should instead split this into two separate commands (config-capture-list
and config-viewer-list
), but I think there's enough benefit in matching the nomenclature of our update command to accept a bit of wonk in this choice.--before
and --after
parameters (or the combination) which will only return bundles from a specific timeframe.--deployed
flag, which can pull it from Param Store.It should be easy to add the other use-cases (filter by MD5, filter by config version, limit responses to specific count) later in case those end up being in high demand. Will create a follow-up ticket to capture them for later consideration.
After playing around with things a bit more, I suspect most people would be satisfied with just the following:
--deployed
flag returns the current/previous config infoGoing to move filtering by --before
and --after
to the list of follow-up features.
Another side-note - calling HeadObject on each config bundle is pretty slow; it takes ~3 seconds to handle 6 config versions. We'll want to take another pass on this, per previous discussion (see https://github.com/arkime/aws-aio/issues/139#issuecomment-1850038929).
Acceptance criteria met; code merged. Resolving.
Description
As a part of https://github.com/arkime/aws-aio/issues/87, this task is to add a way to list the code/config bundles that have been deployed to the Capture and Viewer nodes.
Acceptance Criteria