`juju debug-code`

Usage:

juju debug-code [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:

--at (= "all")

Interpreted by the charm for where you want to stop, defaults to ‘all’

--container (= "")

The container name of the target pod

-m, --model (= "")

Model to operate in. Accepts [<controller name>:]<model name>|<model UUID> --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 and actions on a unit.

Valid unit identifiers are:

  • a standard unit ID, such as mysql/0 or;
  • leader syntax of the form /leader, such as mysql/leader.

Similar to ‘juju debug-hooks’ but rather than dropping you into a shell prompt, it runs the hooks and sets the JUJU_DEBUG_AT environment variable. Charms that implement support for this should use it to set breakpoints based on the environment variable.

See the “juju help ssh” for information about SSH related options accepted by the debug-hooks command.


Last updated 5 months ago.