anchor.diff:  `--service-name <name>`:: Specifies the value for the `<ServiceName>` element in
   the metadata. Defaults to `elasticsearch`.
   
  +`--signing-bundle <file_path>`:: Specifies the path to an existing key pair
  +(in PKCS#12 format). The private key of that key pair will be used to sign
  +the metadata file.
  +
  +`--signing-cert <file_path>`:: Specifies the path to an existing certificate (in
  +PEM format) to be used for signing of the metadata file. You must also specify
  +the `--signing-key` parameter. This parameter cannot be used with the
  +`--signing-bundle` parameter.
  +
  +`--signing-key <file_path>`:: Specifies the path to an existing key (in PEM format)
  +to be used for signing of the metadata file. You must also specify the
  +`--signing-cert` parameter. This parameter cannot be used with the
  +`--signing-bundle` parameter.
  +
  +`--signing-key-password <password>`:: Specifies the password for the signing key.
  +It can be used with either the `--signing-key` or the `--signing-bundle` parameters.
  +
   `--realm <name>`:: Specifies the name of the realm for which the metadata
   should be generated. This parameter is required if there is more than 1 `saml`
   realm in your {es} configuration.
  
positive.code: 
  Some SAML Identity Providers will allow you to automatically import a metadata
  file when you configure the Elastic Stack as a Service Provider.
  
  [float]
  === Parameters
  
negative.code: [--attribute <name>] [--service-name <name>]
  [--locale <name>] [--contacts]
  ([--organisation-name <name>] [--organisation-display-name <name>] [--organisation-url <url>])
  ([--signing-bundle <file_path>] | [--signing-cert <file_path>][--signing-key <file_path>])
  [--signing-key-password <password>]
  [-E <KeyValuePair>]
  [-h, --help] ([-s, --silent] | [-v, --verbose])
  --------------------------------------------------
  