These subcommands, actions, and options are available for Bolt.

apply

Usage: bolt apply <manifest.pp>

apply a manifest on a Windows host via WinRM, providing for the password
  bolt apply site.pp -n winrm://winhost -u Administrator -p
apply a manifest on the local machine, a Linux host via SSH, and hosts from a group specified in an inventory file
  bolt apply site.pp -n localhost,nixhost,node_group
apply a manifest on Windows hosts queried from PuppetDB via WinRM as a domain user, prompting for the password
  bolt apply site.pp -q 'inventory[certname] { facts.os.family = "windows" }' --transport winrm -u 'domain\Administrator' -p

  bolt apply site.pp --nodes foo.example.com,bar.example.com

Available options are:
OptionDescription
-n, --nodes NODESAlias for --targetsDeprecated in favor of --targets
-t, --targets TARGETSIdentifies the targets of command.Enter a comma-separated list of target URIs or group names.Or read a target list from an input file '@<file>' or stdin '-'.Example: --targets localhost,node_group,ssh://nix.com:23,winrm://windows.puppet.comURI format is hostSSH is the default protocol; may be ssh, winrm, pcp, local, docker, remoteFor Windows targets, specify the winrm:// protocol if it has not be configuredFor SSH, port defaults to 22For WinRM, port defaults to 5985 or 5986 based on the --ssl setting
-q, --query QUERYQuery PuppetDB to determine the targets
--rerun FILTERRetry on nodes from the last run'all' all nodes that were part of the last run.'failure' nodes that failed in the last run.'success' nodes that succeeded in the last run.
--description DESCRIPTIONDescription to use for the job
-u, --user USERUser to authenticate as
-p, --password [PASSWORD]Password to authenticate with
--password-promptPrompt for user to input password
--private-key KEYPrivate ssh key to authenticate with
--[no-]host-key-checkCheck host keys with SSH
--[no-]sslUse SSL with WinRM
--[no-]ssl-verifyVerify remote host SSL certificate with WinRM
--run-as USERUser to run as using privilege escalation
--sudo-password [PASSWORD]Password for privilege escalation
--sudo-password-promptPrompt for user to input escalation password
-c, --concurrency CONCURRENCYMaximum number of simultaneous connections (default: 100)
-i, --inventoryfile FILEPATHSpecify where to load inventory from (default: ~/.puppetlabs/bolt/inventory.yaml)
--[no-]save-rerunWhether to update the rerun file after this command.
-m, --modulepath MODULESList of directories containing modules, separated by ':'Directories are case-sensitive
--boltdir FILEPATHSpecify what Boltdir to load config from (default: autodiscovered from current working dir)
--configfile FILEPATHSpecify where to load config from (default: ~/.puppetlabs/bolt/bolt.yaml). Directory containing bolt.yaml will be used as the Boltdir.
--transport TRANSPORTSpecify a default transport: ssh, winrm, pcp, local, docker, remote
--connect-timeout TIMEOUTConnection timeout (defaults vary)
--[no-]ttyRequest a pseudo TTY on nodes that support it
--format FORMATOutput format to use: human or json
--[no-]colorWhether to show output in color
-v, --[no-]verboseDisplay verbose logging
--traceDisplay error stack traces
-h, --helpDisplay help
--versionDisplay the version
--debugDisplay debug logging
--noopExecute a task that supports it in noop mode
-e, --execute CODEPuppet manifest code to apply to the targets
--compile-concurrency CONCURRENCYMaximum number of simultaneous manifest block compiles (default: number of cores)

command run

Usage: bolt command <action> <command>

Available actions are:
  run                              Run a command remotely

run hostname on a Windows host via WinRM, providing for the password
  bolt command run hostname -n winrm://winhost -u Administrator -p
run hostname on the local machine, a Linux host via SSH, and hosts from a group specified in an inventory file
  bolt command run hostname -n localhost,nixhost,node_group
run hostname on Windows hosts queried from PuppetDB via WinRM as a domain user, prompting for the password
  bolt command run hostname -q 'inventory[certname] { facts.os.family = "windows" }' --transport winrm -u 'domain\Administrator' -p

Available options are:
OptionDescription
-n, --nodes NODESAlias for --targetsDeprecated in favor of --targets
-t, --targets TARGETSIdentifies the targets of command.Enter a comma-separated list of target URIs or group names.Or read a target list from an input file '@<file>' or stdin '-'.Example: --targets localhost,node_group,ssh://nix.com:23,winrm://windows.puppet.comURI format is hostSSH is the default protocol; may be ssh, winrm, pcp, local, docker, remoteFor Windows targets, specify the winrm:// protocol if it has not be configuredFor SSH, port defaults to 22For WinRM, port defaults to 5985 or 5986 based on the --ssl setting
-q, --query QUERYQuery PuppetDB to determine the targets
--rerun FILTERRetry on nodes from the last run'all' all nodes that were part of the last run.'failure' nodes that failed in the last run.'success' nodes that succeeded in the last run.
--description DESCRIPTIONDescription to use for the job
-u, --user USERUser to authenticate as
-p, --password [PASSWORD]Password to authenticate with
--password-promptPrompt for user to input password
--private-key KEYPrivate ssh key to authenticate with
--[no-]host-key-checkCheck host keys with SSH
--[no-]sslUse SSL with WinRM
--[no-]ssl-verifyVerify remote host SSL certificate with WinRM
--run-as USERUser to run as using privilege escalation
--sudo-password [PASSWORD]Password for privilege escalation
--sudo-password-promptPrompt for user to input escalation password
-c, --concurrency CONCURRENCYMaximum number of simultaneous connections (default: 100)
-i, --inventoryfile FILEPATHSpecify where to load inventory from (default: ~/.puppetlabs/bolt/inventory.yaml)
--[no-]save-rerunWhether to update the rerun file after this command.
-m, --modulepath MODULESList of directories containing modules, separated by ':'Directories are case-sensitive
--boltdir FILEPATHSpecify what Boltdir to load config from (default: autodiscovered from current working dir)
--configfile FILEPATHSpecify where to load config from (default: ~/.puppetlabs/bolt/bolt.yaml). Directory containing bolt.yaml will be used as the Boltdir.
--transport TRANSPORTSpecify a default transport: ssh, winrm, pcp, local, docker, remote
--connect-timeout TIMEOUTConnection timeout (defaults vary)
--[no-]ttyRequest a pseudo TTY on nodes that support it
--format FORMATOutput format to use: human or json
--[no-]colorWhether to show output in color
-v, --[no-]verboseDisplay verbose logging
--traceDisplay error stack traces
-h, --helpDisplay help
--versionDisplay the version
--debugDisplay debug logging

file upload

Usage: bolt file <action>

Available actions are:
  upload <src> <dest>              Upload local file or directory <src> to <dest> on each node

upload a file to a Windows host via WinRM, providing for the password
  bolt file upload /tmp/source /etc/profile.d/login.sh -n winrm://winhost -u Administrator -p
upload a file to the local machine, a Linux host via SSH, and hosts from a group specified in an inventory file
  bolt file upload /tmp/source /etc/profile.d/login.sh -n localhost,nixhost,node_group
upload a file to Windows hosts queried from PuppetDB via WinRM as a domain user, prompting for the password
  bolt file upload /tmp/source /etc/profile.d/login.sh -q 'inventory[certname] { facts.os.family = "windows" }' --transport winrm -u 'domain\Administrator' -p

Available options are:
OptionDescription
-n, --nodes NODESAlias for --targetsDeprecated in favor of --targets
-t, --targets TARGETSIdentifies the targets of command.Enter a comma-separated list of target URIs or group names.Or read a target list from an input file '@<file>' or stdin '-'.Example: --targets localhost,node_group,ssh://nix.com:23,winrm://windows.puppet.comURI format is hostSSH is the default protocol; may be ssh, winrm, pcp, local, docker, remoteFor Windows targets, specify the winrm:// protocol if it has not be configuredFor SSH, port defaults to 22For WinRM, port defaults to 5985 or 5986 based on the --ssl setting
-q, --query QUERYQuery PuppetDB to determine the targets
--rerun FILTERRetry on nodes from the last run'all' all nodes that were part of the last run.'failure' nodes that failed in the last run.'success' nodes that succeeded in the last run.
--description DESCRIPTIONDescription to use for the job
-u, --user USERUser to authenticate as
-p, --password [PASSWORD]Password to authenticate with
--password-promptPrompt for user to input password
--private-key KEYPrivate ssh key to authenticate with
--[no-]host-key-checkCheck host keys with SSH
--[no-]sslUse SSL with WinRM
--[no-]ssl-verifyVerify remote host SSL certificate with WinRM
--run-as USERUser to run as using privilege escalation
--sudo-password [PASSWORD]Password for privilege escalation
--sudo-password-promptPrompt for user to input escalation password
-c, --concurrency CONCURRENCYMaximum number of simultaneous connections (default: 100)
-i, --inventoryfile FILEPATHSpecify where to load inventory from (default: ~/.puppetlabs/bolt/inventory.yaml)
--[no-]save-rerunWhether to update the rerun file after this command.
-m, --modulepath MODULESList of directories containing modules, separated by ':'Directories are case-sensitive
--boltdir FILEPATHSpecify what Boltdir to load config from (default: autodiscovered from current working dir)
--configfile FILEPATHSpecify where to load config from (default: ~/.puppetlabs/bolt/bolt.yaml). Directory containing bolt.yaml will be used as the Boltdir.
--transport TRANSPORTSpecify a default transport: ssh, winrm, pcp, local, docker, remote
--connect-timeout TIMEOUTConnection timeout (defaults vary)
--[no-]ttyRequest a pseudo TTY on nodes that support it
--format FORMATOutput format to use: human or json
--[no-]colorWhether to show output in color
-v, --[no-]verboseDisplay verbose logging
--traceDisplay error stack traces
-h, --helpDisplay help
--versionDisplay the version
--debugDisplay debug logging
--tmpdir DIRThe directory to upload and execute temporary files on the target

group show

Usage: bolt group <action>

Available actions are:
  show                     Show the list of groups in the inventory

Available options are:
OptionDescription
-h, --helpDisplay help
--versionDisplay the version
--debugDisplay debug logging
--format FORMATOutput format to use: human or json
-i, --inventoryfile FILEPATHSpecify where to load inventory from (default: ~/.puppetlabs/bolt/inventory.yaml)
--boltdir FILEPATHSpecify what Boltdir to load config from (default: autodiscovered from current working dir)
--configfile FILEPATHSpecify where to load config from (default: ~/.puppetlabs/bolt/bolt.yaml). Directory containing bolt.yaml will be used as the Boltdir.

inventory show

Usage: bolt inventory <action>

Available actions are:
  show                     Show the list of targets an action would run on

Available options are:
OptionDescription
-n, --nodes NODESAlias for --targetsDeprecated in favor of --targets
-t, --targets TARGETSIdentifies the targets of command.Enter a comma-separated list of target URIs or group names.Or read a target list from an input file '@<file>' or stdin '-'.Example: --targets localhost,node_group,ssh://nix.com:23,winrm://windows.puppet.comURI format is hostSSH is the default protocol; may be ssh, winrm, pcp, local, docker, remoteFor Windows targets, specify the winrm:// protocol if it has not be configuredFor SSH, port defaults to 22For WinRM, port defaults to 5985 or 5986 based on the --ssl setting
-q, --query QUERYQuery PuppetDB to determine the targets
--rerun FILTERRetry on nodes from the last run'all' all nodes that were part of the last run.'failure' nodes that failed in the last run.'success' nodes that succeeded in the last run.
--description DESCRIPTIONDescription to use for the job
-h, --helpDisplay help
--versionDisplay the version
--debugDisplay debug logging
--format FORMATOutput format to use: human or json
-i, --inventoryfile FILEPATHSpecify where to load inventory from (default: ~/.puppetlabs/bolt/inventory.yaml)
--boltdir FILEPATHSpecify what Boltdir to load config from (default: autodiscovered from current working dir)
--configfile FILEPATHSpecify where to load config from (default: ~/.puppetlabs/bolt/bolt.yaml). Directory containing bolt.yaml will be used as the Boltdir.
--detailShow resolved configuration for the targets

plan convert

Usage: bolt plan convert <plan_path>

Available options are:
OptionDescription
-h, --helpDisplay help
--versionDisplay the version
--debugDisplay debug logging
-m, --modulepath MODULESList of directories containing modules, separated by ':'Directories are case-sensitive
--boltdir FILEPATHSpecify what Boltdir to load config from (default: autodiscovered from current working dir)
--configfile FILEPATHSpecify where to load config from (default: ~/.puppetlabs/bolt/bolt.yaml). Directory containing bolt.yaml will be used as the Boltdir.

plan run

Usage: bolt plan run <plan> [parameters]

Parameters are of the form <parameter>=<value>.

run the canary plan on a Windows host via WinRM, providing for the password
  bolt plan run canary command=hostname -n winrm://winhost -u Administrator -p
run the canary plan on the local machine, a Linux host via SSH, and hosts from a group specified in an inventory file
  bolt plan run canary command=hostname -n localhost,nixhost,node_group
run the canary plan on Windows hosts queried from PuppetDB via WinRM as a domain user, prompting for the password
  bolt plan run canary command=hostname -q 'inventory[certname] { facts.os.family = "windows" }' --transport winrm -u 'domain\Administrator' -p

Available options are:
OptionDescription
-n, --nodes NODESAlias for --targetsDeprecated in favor of --targets
-t, --targets TARGETSIdentifies the targets of command.Enter a comma-separated list of target URIs or group names.Or read a target list from an input file '@<file>' or stdin '-'.Example: --targets localhost,node_group,ssh://nix.com:23,winrm://windows.puppet.comURI format is hostSSH is the default protocol; may be ssh, winrm, pcp, local, docker, remoteFor Windows targets, specify the winrm:// protocol if it has not be configuredFor SSH, port defaults to 22For WinRM, port defaults to 5985 or 5986 based on the --ssl setting
-q, --query QUERYQuery PuppetDB to determine the targets
--rerun FILTERRetry on nodes from the last run'all' all nodes that were part of the last run.'failure' nodes that failed in the last run.'success' nodes that succeeded in the last run.
--description DESCRIPTIONDescription to use for the job
-u, --user USERUser to authenticate as
-p, --password [PASSWORD]Password to authenticate with
--password-promptPrompt for user to input password
--private-key KEYPrivate ssh key to authenticate with
--[no-]host-key-checkCheck host keys with SSH
--[no-]sslUse SSL with WinRM
--[no-]ssl-verifyVerify remote host SSL certificate with WinRM
--run-as USERUser to run as using privilege escalation
--sudo-password [PASSWORD]Password for privilege escalation
--sudo-password-promptPrompt for user to input escalation password
-c, --concurrency CONCURRENCYMaximum number of simultaneous connections (default: 100)
-i, --inventoryfile FILEPATHSpecify where to load inventory from (default: ~/.puppetlabs/bolt/inventory.yaml)
--[no-]save-rerunWhether to update the rerun file after this command.
-m, --modulepath MODULESList of directories containing modules, separated by ':'Directories are case-sensitive
--boltdir FILEPATHSpecify what Boltdir to load config from (default: autodiscovered from current working dir)
--configfile FILEPATHSpecify where to load config from (default: ~/.puppetlabs/bolt/bolt.yaml). Directory containing bolt.yaml will be used as the Boltdir.
--transport TRANSPORTSpecify a default transport: ssh, winrm, pcp, local, docker, remote
--connect-timeout TIMEOUTConnection timeout (defaults vary)
--[no-]ttyRequest a pseudo TTY on nodes that support it
--format FORMATOutput format to use: human or json
--[no-]colorWhether to show output in color
-v, --[no-]verboseDisplay verbose logging
--traceDisplay error stack traces
-h, --helpDisplay help
--versionDisplay the version
--debugDisplay debug logging
--params PARAMETERSParameters to a task or plan as json, a json file '@<file>', or on stdin '-'
--compile-concurrency CONCURRENCYMaximum number of simultaneous manifest block compiles (default: number of cores)
--tmpdir DIRThe directory to upload and execute temporary files on the target

plan show

Usage: bolt plan show <plan>

Available actions are:
  show                             Show list of available plans
  show <plan>                      Show details for plan

Available options are:
OptionDescription
-h, --helpDisplay help
--versionDisplay the version
--debugDisplay debug logging
-m, --modulepath MODULESList of directories containing modules, separated by ':'Directories are case-sensitive
--boltdir FILEPATHSpecify what Boltdir to load config from (default: autodiscovered from current working dir)
--configfile FILEPATHSpecify where to load config from (default: ~/.puppetlabs/bolt/bolt.yaml). Directory containing bolt.yaml will be used as the Boltdir.

project init

Usage: bolt project init [directory]

Create a new Bolt project.
Specify a directory to create the Bolt project in. Defaults to the current working directory.

Available options are:
OptionDescription
-h, --helpDisplay help
--versionDisplay the version
--debugDisplay debug logging

project migrate

Usage: bolt project migrate

Migrate a Bolt project to the latest version.
Loads a Bolt project's inventory file and migrates it to the latest version. The
inventory file is modified in place and will not preserve comments or formatting.

Available options are:
OptionDescription
-h, --helpDisplay help
--versionDisplay the version
--debugDisplay debug logging
-i, --inventoryfile FILEPATHSpecify where to load inventory from (default: ~/.puppetlabs/bolt/inventory.yaml)
--boltdir FILEPATHSpecify what Boltdir to load config from (default: autodiscovered from current working dir)
--configfile FILEPATHSpecify where to load config from (default: ~/.puppetlabs/bolt/bolt.yaml). Directory containing bolt.yaml will be used as the Boltdir.

puppetfile generate-types

Usage: bolt puppetfile generate-types

Generate type references to register in Plans
  bolt puppetfile generate-types

Available options are:
OptionDescription
-h, --helpDisplay help
--versionDisplay the version
--debugDisplay debug logging
-m, --modulepath MODULESList of directories containing modules, separated by ':'Directories are case-sensitive
--boltdir FILEPATHSpecify what Boltdir to load config from (default: autodiscovered from current working dir)
--configfile FILEPATHSpecify where to load config from (default: ~/.puppetlabs/bolt/bolt.yaml). Directory containing bolt.yaml will be used as the Boltdir.

puppetfile install

Usage: bolt puppetfile install

Install modules into the local Boltdir
  bolt puppetfile install

Available options are:
OptionDescription
-h, --helpDisplay help
--versionDisplay the version
--debugDisplay debug logging
-m, --modulepath MODULESList of directories containing modules, separated by ':'Directories are case-sensitive
--boltdir FILEPATHSpecify what Boltdir to load config from (default: autodiscovered from current working dir)
--configfile FILEPATHSpecify where to load config from (default: ~/.puppetlabs/bolt/bolt.yaml). Directory containing bolt.yaml will be used as the Boltdir.

puppetfile show-modules

Usage: bolt puppetfile show-modules

List modules available to Bolt
  bolt puppetfile show-modules

Available options are:
OptionDescription
-h, --helpDisplay help
--versionDisplay the version
--debugDisplay debug logging
-m, --modulepath MODULESList of directories containing modules, separated by ':'Directories are case-sensitive
--boltdir FILEPATHSpecify what Boltdir to load config from (default: autodiscovered from current working dir)
--configfile FILEPATHSpecify where to load config from (default: ~/.puppetlabs/bolt/bolt.yaml). Directory containing bolt.yaml will be used as the Boltdir.

script run

Usage: bolt script <action> <script> [[arg1] ... [argN]]

Available actions are:
  run                              Upload a local script and run it remotely

run a script on a Windows host via WinRM, providing for the password
  bolt script run my_script.ps1 some args -n winrm://winhost -u Administrator -p
run a script on the local machine, a Linux host via SSH, and hosts from a group specified in an inventory file
  bolt script run my_script.ps1 some args -n localhost,nixhost,node_group
run a script on Windows hosts queried from PuppetDB via WinRM as a domain user, prompting for the password
  bolt script run my_script.ps1 some args -q 'inventory[certname] { facts.os.family = "windows" }' --transport winrm -u 'domain\Administrator' -p

Available options are:
OptionDescription
-n, --nodes NODESAlias for --targetsDeprecated in favor of --targets
-t, --targets TARGETSIdentifies the targets of command.Enter a comma-separated list of target URIs or group names.Or read a target list from an input file '@<file>' or stdin '-'.Example: --targets localhost,node_group,ssh://nix.com:23,winrm://windows.puppet.comURI format is hostSSH is the default protocol; may be ssh, winrm, pcp, local, docker, remoteFor Windows targets, specify the winrm:// protocol if it has not be configuredFor SSH, port defaults to 22For WinRM, port defaults to 5985 or 5986 based on the --ssl setting
-q, --query QUERYQuery PuppetDB to determine the targets
--rerun FILTERRetry on nodes from the last run'all' all nodes that were part of the last run.'failure' nodes that failed in the last run.'success' nodes that succeeded in the last run.
--description DESCRIPTIONDescription to use for the job
-u, --user USERUser to authenticate as
-p, --password [PASSWORD]Password to authenticate with
--password-promptPrompt for user to input password
--private-key KEYPrivate ssh key to authenticate with
--[no-]host-key-checkCheck host keys with SSH
--[no-]sslUse SSL with WinRM
--[no-]ssl-verifyVerify remote host SSL certificate with WinRM
--run-as USERUser to run as using privilege escalation
--sudo-password [PASSWORD]Password for privilege escalation
--sudo-password-promptPrompt for user to input escalation password
-c, --concurrency CONCURRENCYMaximum number of simultaneous connections (default: 100)
-i, --inventoryfile FILEPATHSpecify where to load inventory from (default: ~/.puppetlabs/bolt/inventory.yaml)
--[no-]save-rerunWhether to update the rerun file after this command.
-m, --modulepath MODULESList of directories containing modules, separated by ':'Directories are case-sensitive
--boltdir FILEPATHSpecify what Boltdir to load config from (default: autodiscovered from current working dir)
--configfile FILEPATHSpecify where to load config from (default: ~/.puppetlabs/bolt/bolt.yaml). Directory containing bolt.yaml will be used as the Boltdir.
--transport TRANSPORTSpecify a default transport: ssh, winrm, pcp, local, docker, remote
--connect-timeout TIMEOUTConnection timeout (defaults vary)
--[no-]ttyRequest a pseudo TTY on nodes that support it
--format FORMATOutput format to use: human or json
--[no-]colorWhether to show output in color
-v, --[no-]verboseDisplay verbose logging
--traceDisplay error stack traces
-h, --helpDisplay help
--versionDisplay the version
--debugDisplay debug logging
--tmpdir DIRThe directory to upload and execute temporary files on the target

secret createkeys

Usage: bolt secret <action> <value>
Manage secrets for inventory and hiera data.

Available actions are:
  createkeys               Create new encryption keys
  encrypt                  Encrypt a value
  decrypt                  Decrypt a value

Available options are:
OptionDescription
-h, --helpDisplay help
--versionDisplay the version
--debugDisplay debug logging
-m, --modulepath MODULESList of directories containing modules, separated by ':'Directories are case-sensitive
--boltdir FILEPATHSpecify what Boltdir to load config from (default: autodiscovered from current working dir)
--configfile FILEPATHSpecify where to load config from (default: ~/.puppetlabs/bolt/bolt.yaml). Directory containing bolt.yaml will be used as the Boltdir.
--plugin PLUGINSelect the plugin to use

secret decrypt

Usage: bolt secret <action> <value>
Manage secrets for inventory and hiera data.

Available actions are:
  createkeys               Create new encryption keys
  encrypt                  Encrypt a value
  decrypt                  Decrypt a value

Available options are:
OptionDescription
-h, --helpDisplay help
--versionDisplay the version
--debugDisplay debug logging
-m, --modulepath MODULESList of directories containing modules, separated by ':'Directories are case-sensitive
--boltdir FILEPATHSpecify what Boltdir to load config from (default: autodiscovered from current working dir)
--configfile FILEPATHSpecify where to load config from (default: ~/.puppetlabs/bolt/bolt.yaml). Directory containing bolt.yaml will be used as the Boltdir.
--plugin PLUGINSelect the plugin to use

secret encrypt

Usage: bolt secret <action> <value>
Manage secrets for inventory and hiera data.

Available actions are:
  createkeys               Create new encryption keys
  encrypt                  Encrypt a value
  decrypt                  Decrypt a value

Available options are:
OptionDescription
-h, --helpDisplay help
--versionDisplay the version
--debugDisplay debug logging
-m, --modulepath MODULESList of directories containing modules, separated by ':'Directories are case-sensitive
--boltdir FILEPATHSpecify what Boltdir to load config from (default: autodiscovered from current working dir)
--configfile FILEPATHSpecify where to load config from (default: ~/.puppetlabs/bolt/bolt.yaml). Directory containing bolt.yaml will be used as the Boltdir.
--plugin PLUGINSelect the plugin to use

task run

Usage: bolt task run <task> [parameters]

Parameters are of the form <parameter>=<value>.

run facter on a Windows host via WinRM, providing for the password
  bolt task run facts -n winrm://winhost -u Administrator -p
run facter on the local machine, a Linux host via SSH, and hosts from a group specified in an inventory file
  bolt task run facts -n localhost,nixhost,node_group
run facter on Windows hosts queried from PuppetDB via WinRM as a domain user, prompting for the password
  bolt task run facts -q 'inventory[certname] { facts.os.family = "windows" }' --transport winrm -u 'domain\Administrator' -p

Available options are:
OptionDescription
-n, --nodes NODESAlias for --targetsDeprecated in favor of --targets
-t, --targets TARGETSIdentifies the targets of command.Enter a comma-separated list of target URIs or group names.Or read a target list from an input file '@<file>' or stdin '-'.Example: --targets localhost,node_group,ssh://nix.com:23,winrm://windows.puppet.comURI format is hostSSH is the default protocol; may be ssh, winrm, pcp, local, docker, remoteFor Windows targets, specify the winrm:// protocol if it has not be configuredFor SSH, port defaults to 22For WinRM, port defaults to 5985 or 5986 based on the --ssl setting
-q, --query QUERYQuery PuppetDB to determine the targets
--rerun FILTERRetry on nodes from the last run'all' all nodes that were part of the last run.'failure' nodes that failed in the last run.'success' nodes that succeeded in the last run.
--description DESCRIPTIONDescription to use for the job
-u, --user USERUser to authenticate as
-p, --password [PASSWORD]Password to authenticate with
--password-promptPrompt for user to input password
--private-key KEYPrivate ssh key to authenticate with
--[no-]host-key-checkCheck host keys with SSH
--[no-]sslUse SSL with WinRM
--[no-]ssl-verifyVerify remote host SSL certificate with WinRM
--run-as USERUser to run as using privilege escalation
--sudo-password [PASSWORD]Password for privilege escalation
--sudo-password-promptPrompt for user to input escalation password
-c, --concurrency CONCURRENCYMaximum number of simultaneous connections (default: 100)
-i, --inventoryfile FILEPATHSpecify where to load inventory from (default: ~/.puppetlabs/bolt/inventory.yaml)
--[no-]save-rerunWhether to update the rerun file after this command.
-m, --modulepath MODULESList of directories containing modules, separated by ':'Directories are case-sensitive
--boltdir FILEPATHSpecify what Boltdir to load config from (default: autodiscovered from current working dir)
--configfile FILEPATHSpecify where to load config from (default: ~/.puppetlabs/bolt/bolt.yaml). Directory containing bolt.yaml will be used as the Boltdir.
--transport TRANSPORTSpecify a default transport: ssh, winrm, pcp, local, docker, remote
--connect-timeout TIMEOUTConnection timeout (defaults vary)
--[no-]ttyRequest a pseudo TTY on nodes that support it
--format FORMATOutput format to use: human or json
--[no-]colorWhether to show output in color
-v, --[no-]verboseDisplay verbose logging
--traceDisplay error stack traces
-h, --helpDisplay help
--versionDisplay the version
--debugDisplay debug logging
--params PARAMETERSParameters to a task or plan as json, a json file '@<file>', or on stdin '-'
--tmpdir DIRThe directory to upload and execute temporary files on the target

task show

Usage: bolt task show <task>

Available actions are:
  show                             Show list of available tasks
  show <task>                      Show documentation for task

Available options are:
OptionDescription
-h, --helpDisplay help
--versionDisplay the version
--debugDisplay debug logging
-m, --modulepath MODULESList of directories containing modules, separated by ':'Directories are case-sensitive
--boltdir FILEPATHSpecify what Boltdir to load config from (default: autodiscovered from current working dir)
--configfile FILEPATHSpecify where to load config from (default: ~/.puppetlabs/bolt/bolt.yaml). Directory containing bolt.yaml will be used as the Boltdir.
Back to top
The page rank or the 1 our of 5 rating a user has given the page.
The email address of the user submitting feedback.
The URL of the page being ranked/rated.