Project

General

Profile

Actions

Feature #25706

closed

Disable (sub)-commands

Added by Bernhard Suttner over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

It should be possible to disable commands / subcommands by config file setting.

Actions #1

Updated by The Foreman Bot over 5 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_maintain/pull/238 added
Actions #2

Updated by Martin Bacovsky over 5 years ago

Could you please explain why it should be possible? It is not common behavior of CLI tools so it would be great to have more background information and use cases.

Actions #3

Updated by Bernhard Suttner over 5 years ago

It's mainly because of the snapshot backup strategy. This strategy requires a very specific partition set of LVM - and it requires LVM, too. Online and Offline backup strategy should work on all hosts but snapshot depends on the partitioning. Therefore, we want to hide this command. Additionally, I don't want to bother user (=admins) with options, which don't work. We don't want to document this option and completely hide it.

One more use case would be, that whole main commands shouldn't be visible. Like, on a foreman / katello (or even satellite), the admin doesn't want to use backup at all as the system will be backed up using vmware snapshot or a 3rd party backup tool. Same use case would make sense to disable features like "advanced" or "upgrade".

Actions #4

Updated by Anonymous over 5 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF