juju destroy-model [options] [<controller name>:]<model name>
Terminate all machines/containers and resources for a non-controller model.
--debug (= false)
Equivalent to --show-log --logging-config==DEBUG
-h, --help (= false)
Show help on a command or other topic.
--logging-config (= "")
Specify log levels for modules
--quiet (= false)
Show no informational output
--show-log (= false)
If set, write the log file to stderr
--verbose (= false)
Show more verbose output
-B, --no-browser-login (= false)
Do not use web browser for authentication
--destroy-storage (= false)
Destroy all storage instances in the model
--force (= false)
Force destroy model ignoring any errors
--no-wait (= false)
Rush through model destruction without waiting for each individual step to complete
--release-storage (= false)
Release all storage instances from the model, and management of the controller, without destroying them
-t, --timeout (= 30m0s)
Timeout before model destruction is aborted
-y, --yes (= false)
Do not prompt for confirmation
Destroys the specified model. This will result in the non-recoverable removal of all the units operating in the model and any resources stored there. Due to the irreversible nature of the command, it will prompt for confirmation (unless overridden with the ‘-y’ option) before taking any action.
If there is persistent storage in any of the models managed by the controller, then you must choose to either destroy or release the storage, using --destroy-storage or --release-storage respectively.
Sometimes, the destruction of the model may fail as Juju encounters errors and failures that need to be dealt with before a model can be destroyed. However, at times, there is a need to destroy a model ignoring all operational errors. In these rare cases, use --force option but note that --force will also remove all units of the application, its subordinates and, potentially, machines without given them the opportunity to shutdown cleanly.
Model destruction is a multi-step process. Under normal circumstances, Juju will not proceed to the next step until the current step has finished. However, when using --force, users can also specify --no-wait to progress through steps without delay waiting for each step to complete.
juju destroy-model test juju destroy-model -y mymodel juju destroy-model -y mymodel --timeout 5m juju destroy-model -y mymodel --destroy-storage juju destroy-model -y mymodel --release-storage juju destroy-model -y mymodel --force juju destroy-model -y mymodel --force --no-wait
Last updated 5 months ago.