From ba321551e46caa9e4dd3a72a910020be4a22936c Mon Sep 17 00:00:00 2001
From: vmaneagit <79709341+vmaneagit@users.noreply.github.com>
Date: Fri, 5 Mar 2021 15:51:52 +0200
Subject: [PATCH] Update nodefirmware.ronn

OPTIONS section has been added to match the output from nodefirmware -h
---
 confluent_client/doc/man/nodefirmware.ronn | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/confluent_client/doc/man/nodefirmware.ronn b/confluent_client/doc/man/nodefirmware.ronn
index 12234686..137cc0c7 100644
--- a/confluent_client/doc/man/nodefirmware.ronn
+++ b/confluent_client/doc/man/nodefirmware.ronn
@@ -26,6 +26,15 @@ the out of band facilities.  Firmware updates can end in one of three states:
 * `pending`:  The firmware update process has completed, but the firmware will not be active until the relevant component next resets.  Generally speaking, for UEFI update the system will need a reboot, and for BMC updates, the `nodebmcreset` command will begin the process to activate the firmware.
 * `complete`:  The firmware update process has completed and activation has proceeded.  Note that while the activation process has commenced, the component may still be in the process of rebooting when nodefirmware exits.
 
+## OPTIONS
+
+* `-b`, `--backup`:
+  Target a backup bank rather than primary
+  
+* `-m`, `--maxnodes`:
+  When updating, prompt if more than the specified number of servers will 
+  be affected  
+
 ## EXAMPLES
 
 * Pull firmware from a node: