Bug #15556
closed
Plugin enable options are confusing
Added by Stephen Benjamin over 8 years ago.
Updated over 6 years ago.
Category:
foreman-installer script
|
Description
Every plugin has 2 options like this:
--[no-]enable-foreman-plugin-remote-execution Enable 'foreman_plugin_remote_execution' puppet module (default: false)
--foreman-proxy-plugin-remote-execution-ssh-enabled Enables/disables the plugin (default: true)
The former is really the one to use to actually enabling the plugin, the latter only triggers the .yml config enable option.
It's very confusing for end users who probably see the second option first as it's near the end of the --help.
Related issues
1 (1 open — 0 closed)
- Related to Feature #9308: Add hooks to enable multiple plugin parameters for plugins added
Maybe something that could be solved by #9308?
The enable parameter could be put into an "Advanced" documentation group so it doesn't usually show up in the help output.
- Bugzilla link set to 1352003
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/puppet-foreman_proxy/pull/264 added
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Translation missing: en.field_release set to 160
- Assignee set to Julian Todt
- Pull request https://github.com/theforeman/puppet-foreman_proxy/pull/434 added
- Assignee changed from Julian Todt to Stephen Benjamin
- Triaged set to No
- Pull request deleted (
https://github.com/theforeman/puppet-foreman_proxy/pull/434)
Also available in: Atom
PDF