Open refcell opened 1 year ago
I'll take this one if nobody else is on it
go for it ser!
This really comes handy for debugging the stages module which I'm working on, @roninjin10 did you have any luck with it yet?
The logic behind building a stage manager orchestrator from the stack config is so that it can handle finding existing running stack components based on the configuration.
All opup components are tagged with a com.docker.compose.project=op-up
label, so for now a minimal version would just be to stop and remove all running docker containers with this label, regardless of the stack.toml
file which we don't have just yet.
Hey @merklefruit sorry for delay been super busy with 3 projects I'm working on. I plan on starting on this this weekend and contributing semi regularly starting tomorrow. I've read the rust book 3 times but have written very little so I may be slow even once I start though
No worries at all sir!
Description
As part of #17, this task is to introduce a new
down
subcommand toop-up
that winds down the op-stack defined by the localstack.toml
configuration file.Since this is a destructive action, it should use
inquire
to prompt the user to confirm running the command.The logic of winding down a stack based on the config should be abstracted into the Stage Manager orchestrator (doesn't exist yet). This allows the
opup
cli binary to build the stage manager from the config, and then be able to wind down the stack via a simpledown() -> eyre::Result<()>
call.For example
The logic behind building a stage manager orchestrator from the stack config is so that it can handle finding existing running stack components based on the configuration. This separates concerns whereby the stack configuration solely handles component and stack configuration while the stage manager can handle orchestrating the stack stages/components.
Since the stage manager
.down()
call is very minimal, thedown
subcommand logic can be placed insidecli.rs
alongside subcommand dispatching.