Closed chelma closed 8 months ago
Thinking through the user experience a bit, we currently have the following:
config-update
scans both the Capture and Viewer config directories for changes. If some are detected, it makes a new .zip, sticks it in s3, and bounces the appropriate ECS service.--force-bounce-capture
, --force-bounce-viewer
, or both to ensure the ECS service(s) get restarted.The other, new commands (config-list
, config-pull
) now segregate actions along the Capture/Viewer lines using flags. To create a more consistent experience across the commands, and satisfy this ticket's acceptance criteria, we could do the following:
config-update
stays the same--capture
or --viewer
flags to operate on just that component--force-bounce-capture
and --force-bounce-viewer
are replaced with --force-bounce
--force-bounce
without --capture
or --viewer
, it bounces both--config-version
to deploy a historical version of the configuration to either the --capture
or --viewer
component (but not both in a single command).Code merged; acceptance criteria met. Resolving.
Description
As a part of https://github.com/arkime/aws-aio/issues/87, this task is to add a way to deploy a specific configuration version to an existing Arkime Cluster.
Acceptance Criteria