Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-36612

Do not use `--force` to approve dangerous changes

    • pcs-0.11.7-5.el10
    • None
    • Moderate
    • rhel-sst-high-availability
    • ssg_filesystems_storage_and_HA
    • 13
    • 23
    • 3
    • False
    • Hide

      None

      Show
      None
    • Yes
    • None
    • Enhancement
    • Hide
      .New `--yes` flag to confirm potentially destructive actions

      To confirm potentially destructive actions such as destroying a cluster, unblocking quorum, or confirming a node being fenced, the `pcs` command-line interface now supports the `--yes` flag. Previously, you could confirm these actions by using the `--force` flag, which is also used for overriding validation errors. With these two functions combined in a single flag, a user could inadvertently confirm a potentially destructive action when the intention is only to override a validation error. You should now use the `--force` flag to override validation errors, and you should use the `--yes` flag to confirm potentially destructive actions.


      Show
      .New `--yes` flag to confirm potentially destructive actions To confirm potentially destructive actions such as destroying a cluster, unblocking quorum, or confirming a node being fenced, the `pcs` command-line interface now supports the `--yes` flag. Previously, you could confirm these actions by using the `--force` flag, which is also used for overriding validation errors. With these two functions combined in a single flag, a user could inadvertently confirm a potentially destructive action when the intention is only to override a validation error. You should now use the `--force` flag to override validation errors, and you should use the `--yes` flag to confirm potentially destructive actions.
    • Done
    • None

      The --force flag is currently used for two purposes:

      • override validation errors
      • proceed with dangerous actions - e.g. cluster destroy, quorum unblock, etc.

      This may cause issues, as users may inadvertently allow an action while they only wanted to override a validation error.

      To resolve this issue, a new flag should be introduced for allowing dangerous actions, and --force should be kept only for overriding validation errors.

              mmazoure Michal Mazourek
              tojeline@redhat.com Tomas Jelinek
              Tomas Jelinek Tomas Jelinek
              Michal Mazourek Michal Mazourek
              Steven Levine Steven Levine
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: