Bug 2218: Fix command for `juju run-action`
Change-Id: Ife2e8e9f532f3c67c7e2f71d3f77d3e4e7dc5257
Signed-off-by: Daniel Arndt <daniel.arndt@canonical.com>
diff --git a/installers/charm/osm-lcm/config.yaml b/installers/charm/osm-lcm/config.yaml
index ac15a0e..e539f7b 100644
--- a/installers/charm/osm-lcm/config.yaml
+++ b/installers/charm/osm-lcm/config.yaml
@@ -54,14 +54,14 @@
type: boolean
description: |
Great for OSM Developers! (Not recommended for production deployments)
-
+
This action activates the Debug Mode, which sets up the container to be ready for debugging.
As part of the setup, SSH is enabled and a VSCode workspace file is automatically populated.
After enabling the debug-mode, execute the following command to get the information you need
to start debugging:
- `juju run-action get-debug-mode-information <unit name> --wait`
-
+ `juju run-action <unit name> get-debug-mode-information --wait`
+
The previous command returns the command you need to execute, and the SSH password that was set.
See also:
@@ -79,7 +79,7 @@
$ git clone "https://osm.etsi.org/gerrit/osm/LCM" /home/ubuntu/LCM
$ juju config lcm lcm-hostpath=/home/ubuntu/LCM
- This configuration only applies if option `debug-mode` is set to true.
+ This configuration only applies if option `debug-mode` is set to true.
n2vc-hostpath:
type: string
description: |
@@ -101,4 +101,4 @@
$ git clone "https://osm.etsi.org/gerrit/osm/common" /home/ubuntu/common
$ juju config lcm common-hostpath=/home/ubuntu/common
- This configuration only applies if option `debug-mode` is set to true.
+ This configuration only applies if option `debug-mode` is set to true.