[brooklyn-docs] 04/04: Explain example where SshCliTool might be needed

[he...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

heneveld pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git

commit ad03da50a0baf65d68a78d5d0ce4627b080d9ef5
Author: Mykola Mandra <my...@cloudsoft.io>
AuthorDate: Tue Aug 30 12:01:18 2022 +0100

    Explain example where SshCliTool might be needed
    
    Signed-off-by: Mykola Mandra <my...@cloudsoft.io>
---
 guide/locations/_clouds.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/guide/locations/_clouds.md b/guide/locations/_clouds.md
index a026a0f3..ef59924b 100644
--- a/guide/locations/_clouds.md
+++ b/guide/locations/_clouds.md
@@ -238,9 +238,11 @@ For more keys and more detail on the keys below, see
 
 - Use `sshToolClass: classname` to configure Apache Brooklyn to use a particular SSH Tool
   installed into the system. The default is to use the SSHJ java library which is a good choice in most instances.
-  Brooklyn also includes `org.apache.brooklyn.util.core.internal.ssh.cli.SshCliTool` which can be used to delegate 
-  to the OS `ssh` command instead, which can be useful if SSH activity is restricted in the environment where Brooklyn is running.
-  Other tools can also be developed and installed.
+  Brooklyn also includes `org.apache.brooklyn.util.core.internal.ssh.cli.SshCliTool` which can be used to delegate to
+  the OS `ssh` command instead. This can be useful if SSH activity is restricted in the environment where Brooklyn is
+  running, such as a specific SSH client being mandated, or if FIPS support or specific cryptography is required which
+  is not supported with the default `sshj` java library used by Brooklyn. Other custom tool classes can also be
+  developed and installed.
 
 - When `org.apache.brooklyn.util.core.internal.ssh.cli.SshCliTool` is set to delegate the OS `ssh` command, then 
   location can have a custom `ssh` and `scp` executable configured, via `sshExecutable` and `scpExecutable` properties: