Vault Options:
    --vault-address
            IP address of the HashiCorp Vault server (mandatory).

    --vault-port
            Port of the HashiCorp Vault server (default: '8200').

    --vault-protocol
            HTTP of the HashiCorp Vault server. Can be: 'http', 'https'
            (default: http).

    --auth-method
            Authentication method to log in against the Vault server. Can
            be: 'azure', 'cert', 'github', 'ldap', 'okta', 'radius',
            'userpass' (default: 'token');

    --auth-path
            Authentication path for 'userpass'. Is an optional setting.

            More information here:
            https://developer.hashicorp.com/vault/docs/auth/userpass#configu
            ration

    --vault-token
            Directly specify a valid token to log in (only for
            --auth-method='token').

    --auth-settings
            Required information to log in according to the selected method.
            Examples: for 'userpass': --auth-settings='username=user1'
            --auth-settings='password=my_password' for 'azure':
            --auth-settings='role=my_azure_role'
            --auth-settings='jwt=my_azure_token'

            More information here: https://www.vaultproject.io/api-docs/auth

    --secret-path
            Location of the secret in the Vault K/V engine (mandatory - Can
            be multiple). Examples: for v1 engine:
            --secret-path='mysecrets/servicecredentials' for v2 engine:
            --secret-path='mysecrets/data/servicecredentials?version=12'

            More information here:
            https://www.vaultproject.io/api-docs/secret/kv

    --map-option
            Overload Plugin option with K/V values. Use the following
            syntax: the_option_to_overload='%{key_$secret_path$}' or
            the_option_to_overload='%{value_$secret_path$}' Example:
            --map-option='username=%{key_mysecrets/servicecredentials}'
            --map-option='password=%{value_mysecrets/servicecredentials}'