anchor.diff:  
   The following are available options:
   
  -* `-o,--operation <arg>` File operation (install | backup | restore)
  -* `-b,--backupDir <arg>` Backup NiFi Directory (used with backup or restore operation)
  -* `-c,--nifiCurrentDir <arg>` Current NiFi Installation Directory (used optionally with install or restore operation)
  -* `-d,--nifiInstallDir <arg>` NiFi Installation Directory (used with install or restore operation)
  -* `-i,--installFile <arg>` NiFi Install File (used with install operation)
  -* `-r,--nifiRollbackDir <arg>` NiFi Installation Directory (used with install or restore operation)
  -* `-t,--bootstrapConf <arg>` Current NiFi Bootstrap Configuration File (used optionally)
  -* `-m,--moveRepositories` Allow repositories to be moved to new/restored nifi directory from existing installation, if available (used optionally with install or restore operation)
  -* `-x,--overwriteConfigs` Overwrite existing configuration directory with upgrade changes (used optionally with install or restore operation)
  -* `-v,--verbose` Verbose messaging (optional)
  -* `-h,--help` Print help info (optional)
  +* `-b`,`--backupDir <arg>`          Backup NiFi Directory (used with backup or restore operation)
  +* `-c`,`--nifiCurrentDir <arg>`     Current NiFi Installation Directory (used optionally with install or restore operation)
  +* `-d`,`--nifiInstallDir <arg>`     NiFi Installation Directory (used with install or restore operation)
  +* `-h`,`--help`                     Print help info (optional)
  +* `-i`,`--installFile <arg>`        NiFi Install File (used with install operation)
  +* `-m`,`--moveRepositories`         Allow repositories to be moved to new/restored nifi directory from existing installation, if available (used optionally with install or restore operation)
  +* `-o`,`--operation <arg>`          File operation (install | backup | restore)
  +* `-r`,`--nifiRollbackDir <arg>`    NiFi Installation Directory (used with install or restore operation)
  +* `-t`,`--bootstrapConf <arg>`      Current NiFi Bootstrap Configuration File (used optionally)
  +* `-v`,`--verbose`                  Verbose messaging (optional)
  +* `-x`,`--overwriteConfigs`         Overwrite existing configuration directory with upgrade changes (used optionally with install or restore operation)
   
   Example usage on Linux:
   
  
positive.code: 
  Client/Server
  ^^^^^^^^^^^^^
  Client/Server mode relies on a long-running Certificate Authority (CA) to issue certificates.  The CA can be stopped when you’re not bringing nodes online.
  
  
  ===== Server
  
  The CA server is invoked by running `./bin/tls-toolkit server -h` prints the usage information along with descriptions of options that can be specified.
  
  The most common options to specify are:
  
  * `-f,--configJson`        The location of the json config (written after first run)
  * `-F,--useConfigJson`     Loads all relevant configuration from the config json (configJson is the only other argument necessary)
  * `-t,--token`             The token used to prevent man in the middle attacks (this should be a long, random value and needs to be known when invoking the client)
  * `-D,--dn`                The DN for the CA
  
  ===== Client
  
  The client can be used to request new Certificates from the CA.  The client utility generates a keypair and Certificate Signing Request (CSR) and sends the CSR to the Certificate Authority.  The client is invoked by running `./bin/tls-toolkit.sh client -h` which prints the usage information along with descriptions of options that can be specified.
  
  The most common options to specify are:
  
  * `-f,--configJson`                   The json config file
  * `-c,--certificateAuthorityHostname`  The hostname of the CA
  * `-D,--DN`                            The DN for the CSR (and Certificate)
  * `-t,--token`                         The token used to prevent man in the middle attacks (this should be a long, random value and needs to be the same one used to start the CA server)
  * `-T,--keyStoreType`                  The type of keystore to create (leave default for NiFi nodes, specify PKCS12 to create client cert)
  
  After running the client you will have the CA’s certificate, a keystore, a truststore, and a config.json with information about them as well as their passwords.
  
  For a client certificate that can be easily imported into the browser, specify: `-T PKCS12`
  
  
negative.code: 
  The following are available options:
  
  * `-b`,`--bootstrapConf <arg>`      Existing Bootstrap Configuration file (required)
  * `-d`,`--nifiInstallDir <arg>`     NiFi Root Folder (required)
  * `-h`,`--help`                     Help Text (optional)
  * `-l`,`--level <arg>`              Status level of bulletin – INFO, WARN, ERROR
  * `-m`,`--message <arg>`            Bulletin message (required)
  * `-p`,`--proxyDN <arg>`            Proxy or User DN (required for secured nodes)
  * `-v`,`--verbose`                  Verbose messaging (optional)
  
  
  Example usage on Linux:
  
  