`juju debug-hooks`
Usage:
juju debug-hooks [options] <unit name> [hook or action names]
Summary:
Launch a tmux session to debug hooks and/or actions.
Global Options:
--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
Command Options:
--container (= "")
The container name of the target pod
-m, --model (= "")
Model to operate in. Accepts [:]|
--no-host-key-checks (= false)
Skip host key checking (INSECURE)
--proxy (= false)
Proxy through the API server
--pty (= <auto>)
Enable pseudo-tty allocation
--remote (= false)
Target on the workload or operator pod (k8s-only)
Details:
Interactively debug hooks or actions remotely on an application unit.
Valid unit identifiers are:
- a standard unit ID, such as mysql/0 or;
- leader syntax of the form /leader, such as mysql/leader.
See the “juju help ssh” for information about SSH related options accepted by the debug-hooks command.
Aliases:
debug-hook
Last updated 1 year, 3 months ago.