feat(bin): Nuke Subcommand #19
Labels
A-bin
Area: Binary related
alpha
C-feature
Category: Features
M-good-first-issue
Meta: Good first issue
Description
As part of #17, this task is to introduce a convenience
nuke
subcommand that nukes all runningop-up
stack components (including cleaning/pruning any docker containers, images, and volumes). Since this is a destructive command, it should useinquire
to prompt the user to confirm that they want to perform the given actions (described in detail before the confirmation prompt).Nuking logic should be entirely handled by the
StageManager
system orchestrator.The extent of how to nuke stacks should be managed through cli flags and passed into the
StageManager
when executing thenuke()
call. Since nuking also involves the local stack, theopup
cli binary should build theStageManager
from the config, and then callnuke() -> eyre::Result<()>
. How the nuke cli flags are configured in theStageManager
when building from theconfig
or passing them directly in thenuke()
call as arguments is an implementation detail, that is up to the implementor.For example
Since the cli binary logic is minimal, it should be placed inside the
cli.rs
file where subcommand dispatching is handled.The text was updated successfully, but these errors were encountered: