puppet job run command options

You might want to use these options with the puppet job run command. Alternately, use puppet job --help to get a complete list of options you can use with puppet job commands.

Option	Description
--noop	A flag indicating whether to run the job in no-op mode. No-op mode simulates changes from a new catalog without actually enforcing the changes. Excluding this option assumes noop = false, unless noop is specified elsewhere, such as the agent's puppet.conf file. Cannot be used in conjunction with --no-noop.
--no-noop	A flag indicating whether to run the job in enforcement mode and enforce a new catalog on all targeted nodes. This flag overrides noop = true if set in the agent's puppet.conf file. Cannot be used in conjunction with --noop.
--environment or -e	Supply an environment name, as a string, to override the environment specified in the orchestrator configuration file. The orchestrator uses this option to tell nodes which environment to run the job in. If any nodes can’t run in the specified environment, those node runs fail. A node can run in an environment as long as it is classified into that environment in the PE node classifier.
--no-enforce-environment	A flag indicating whether you want the job to ignore the environment set by the --environment flag. When you use this flag, agents run in the environment specified by the PE Node Manager or their puppet.conf files.
--description	Supply a description of the job, as a string. The description appears on the job list and job details pages, and it is returned when you use the puppet job show command.
--concurrency	Supply an integer specifying the maximum number of nodes to run at one time. The default is an unlimited number of nodes. You can also configure concurrent compile requests in the console.