Revision 9a23ee14
Added by Stephen Benjamin almost 8 years ago
| manifests/plugin/remote_execution/ssh.pp | ||
|---|---|---|
|
#
|
||
|
# === Parameters:
|
||
|
#
|
||
|
# $enabled:: Enables/disables the plugin
|
||
|
# type:boolean
|
||
|
#
|
||
|
# $listen_on:: Proxy feature listens on https, http, or both
|
||
|
#
|
||
|
# $generate_keys:: Automatically generate SSH keys
|
||
|
# type:boolean
|
||
|
#
|
||
| ... | ... | |
|
#
|
||
|
# $remote_working_dir:: Remote working directory on clients
|
||
|
#
|
||
|
# === Advanced parameters:
|
||
|
#
|
||
|
# $enabled:: Enables/disables the plugin
|
||
|
# type:boolean
|
||
|
#
|
||
|
# $listen_on:: Proxy feature listens on https, http, or both
|
||
|
#
|
||
|
class foreman_proxy::plugin::remote_execution::ssh (
|
||
|
$enabled = $::foreman_proxy::plugin::remote_execution::ssh::params::enabled,
|
||
|
$listen_on = $::foreman_proxy::plugin::remote_execution::ssh::params::listen_on,
|
||
Also available in: Unified diff
fixes #15556 - move some params to advanced (#264)
This reduces the amount of default help text and confusing options for
plugins. This is especially confusing for 'enabled' as there are 2
options:
```
--[no-]enable-foreman-proxy-plugin-remote-execution-ssh
--foreman-proxy-plugin-remote-execution-ssh-enabled
```
The former REALLY enables the plugin, the latter is only controlling
the value in the .yml configuration which has a sane default value.
We should hide this, and some of the other options like `listen_on`,
`group`, etc which probably don't need changing ever.