runCommand -package:structured-cli -package:github-release -package:io-streams -package:graphviz -package:mongoDB -package:quickcheck-state-machine -package:hledger -package:process -package:xmonad-contrib

Either calls the given continuation, prints help text and calls exitSuccess, or prints an error and calls exitFailure. See runSubcommand for details on subcommand support.

Execute a Command.

Run a command within the PlotM monad. Stderr stream is read and decoded, while Stdout is ignored. Logging happens at the debug level if the command succeeds, or at the error level if it does not succeed.

Run with the given middleware and parsing options from the command line. Since 2.0.1

Called before a command is about to run. The first argument is the step index and the second is a string representing the command about to be run.

Currently, we support including only one RunCommandTarget block, which specifies either an array of InstanceIds or a tag.

Can be either tag: tag-key or InstanceIds.

If Key is tag: tag-key, Values is a list of tag values. If Key is InstanceIds, Values is a list of Amazon EC2 instance IDs.

This parameter contains the criteria (either InstanceIds or a tag) used to specify which EC2 instances are to be sent the command. See: newRunCommandParameters smart constructor.

Information about the EC2 instances that are to be sent the command, specified as key-value pairs. Each RunCommandTarget block can include only one key, but this key may specify multiple values. See: newRunCommandTarget smart constructor.

Default to True. Should you run command line actions, set to False to skip actions whose output streams and exit code are not used. Useful for profiling the non-command portion of the build system.

Create a value of RunCommandParameters with all optional fields omitted. Use generic-lens or optics to modify other optional fields. The following record fields are available, with the corresponding lenses provided for backwards compatibility: $sel:runCommandTargets:RunCommandParameters', runCommandParameters_runCommandTargets - Currently, we support including only one RunCommandTarget block, which specifies either an array of InstanceIds or a tag.

Create a value of RunCommandTarget with all optional fields omitted. Use generic-lens or optics to modify other optional fields. The following record fields are available, with the corresponding lenses provided for backwards compatibility: $sel:key:RunCommandTarget', runCommandTarget_key - Can be either tag: tag-key or InstanceIds. $sel:values:RunCommandTarget', runCommandTarget_values - If Key is tag: tag-key, Values is a list of tag values. If Key is InstanceIds, Values is a list of Amazon EC2 instance IDs.

Parameters used when you are using the rule to invoke Amazon EC2 Run Command.

The parameters for a RUN_COMMAND task type. For information about specifying and updating task parameters, see RegisterTaskWithMaintenanceWindow and UpdateMaintenanceWindowTask. LoggingInfo has been deprecated. To specify an Amazon Simple Storage Service (Amazon S3) bucket to contain logs, instead use the OutputS3BucketName and OutputS3KeyPrefix options in the TaskInvocationParameters structure. For information about how Amazon Web Services Systems Manager handles these options for the supported maintenance window task types, see MaintenanceWindowTaskInvocationParameters. TaskParameters has been deprecated. To specify parameters to pass to a task when it runs, instead use the Parameters option in the TaskInvocationParameters structure. For information about how Systems Manager handles these options for the supported maintenance window task types, see MaintenanceWindowTaskInvocationParameters. For RUN_COMMAND tasks, Systems Manager uses specified values for TaskParameters and LoggingInfo only if no values are specified for TaskInvocationParameters. See: newMaintenanceWindowRunCommandParameters smart constructor.