Actions
Bug #15556
closed
Plugin enable options are confusing
Status:
Closed
Priority:
Normal
Assignee:
Category:
foreman-installer script
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
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.
Updated by Stephen Benjamin over 8 years ago
- Related to Feature #9308: Add hooks to enable multiple plugin parameters for plugins added
Updated by Stephen Benjamin over 8 years ago
Maybe something that could be solved by #9308?
Updated by Dominic Cleal over 8 years ago
The enable parameter could be put into an "Advanced" documentation group so it doesn't usually show up in the help output.
Updated by Stephen Benjamin over 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/puppet-foreman_proxy/pull/264 added
Updated by Anonymous over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset puppet-foreman_proxy|9a23ee14413400bfa7f0e6216fd8aeb14aaa1667.
Updated by Dominic Cleal over 8 years ago
- Translation missing: en.field_release set to 160
Updated by The Foreman Bot over 6 years ago
- Assignee set to Julian Todt
- Pull request https://github.com/theforeman/puppet-foreman_proxy/pull/434 added
Updated by Ewoud Kohl van Wijngaarden over 6 years ago
- Assignee changed from Julian Todt to Stephen Benjamin
- Triaged set to No
- Pull request deleted (
https://github.com/theforeman/puppet-foreman_proxy/pull/434)
Actions