feat(client-ssm): Update the StartChangeRequestExecution, adding TargetMaps to the Runbook parameter

Author: awstools

clients/client-ssm/src/SSM.ts

@@ -707,11 +707,11 @@ import { SSMClient } from "./SSMClient";
 export class SSM extends SSMClient {
   /**
    * <p>Adds or overwrites one or more tags for the specified resource. Tags are metadata that you
-   *    can assign to your automations, documents, managed nodes, maintenance windows, Parameter Store parameters, and
-   *    patch baselines. Tags enable you to categorize your resources in different ways, for example, by
-   *    purpose, owner, or environment. Each tag consists of a key and an optional value, both of which
-   *    you define. For example, you could define a set of tags for your account's managed nodes that
-   *    helps you track each node's owner and stack level. For example:</p>
+   *    can assign to your automations, documents, managed nodes, maintenance windows, Parameter Store
+   *    parameters, and patch baselines. Tags enable you to categorize your resources in different ways,
+   *    for example, by purpose, owner, or environment. Each tag consists of a key and an optional value,
+   *    both of which you define. For example, you could define a set of tags for your account's managed
+   *    nodes that helps you track each node's owner and stack level. For example:</p>
    *          <ul>
    *             <li>
    *                <p>
@@ -744,7 +744,8 @@ export class SSM extends SSMClient {
    *                </p>
    *             </li>
    *          </ul>
-   *          <p>Most resources can have a maximum of 50 tags. Automations can have a maximum of 5 tags.</p>
+   *          <p>Most resources can have a maximum of 50 tags. Automations can have a maximum of 5
+   *    tags.</p>
    *          <p>We recommend that you devise a set of tag keys that meets your needs for each resource type.
    *    Using a consistent set of tag keys makes it easier for you to manage your resources. You can
    *    search and filter the resources based on the tags you add. Tags don't have any semantic meaning
@@ -3322,13 +3323,13 @@ export class SSM extends SSMClient {
 
   /**
    * <p>Retrieves the details of a maintenance window task.</p>
-   *  	       <note>
-   *  		         <p>For maintenance window tasks without a specified target, you can't supply values for
-   *  			<code>--max-errors</code> and <code>--max-concurrency</code>. Instead, the system inserts a
-   *  			placeholder value of <code>1</code>, which may be reported in the response to this command.
-   *  			These values don't affect the running of your task and can be ignored.</p>
-   *  	       </note>
-   *  	       <p>To retrieve a list of tasks in a maintenance window, instead use the <a>DescribeMaintenanceWindowTasks</a> command.</p>
+   *          <note>
+   *             <p>For maintenance window tasks without a specified target, you can't supply values for
+   *      <code>--max-errors</code> and <code>--max-concurrency</code>. Instead, the system inserts a
+   *     placeholder value of <code>1</code>, which may be reported in the response to this command.
+   *     These values don't affect the running of your task and can be ignored.</p>
+   *          </note>
+   *          <p>To retrieve a list of tasks in a maintenance window, instead use the <a>DescribeMaintenanceWindowTasks</a> command.</p>
    */
   public getMaintenanceWindowTask(
     args: GetMaintenanceWindowTaskCommandInput,

clients/client-ssm/src/commands/AddTagsToResourceCommand.ts

@@ -23,11 +23,11 @@ export interface AddTagsToResourceCommandOutput extends AddTagsToResourceResult,
 
 /**
  * <p>Adds or overwrites one or more tags for the specified resource. Tags are metadata that you
- *    can assign to your automations, documents, managed nodes, maintenance windows, Parameter Store parameters, and
- *    patch baselines. Tags enable you to categorize your resources in different ways, for example, by
- *    purpose, owner, or environment. Each tag consists of a key and an optional value, both of which
- *    you define. For example, you could define a set of tags for your account's managed nodes that
- *    helps you track each node's owner and stack level. For example:</p>
+ *    can assign to your automations, documents, managed nodes, maintenance windows, Parameter Store
+ *    parameters, and patch baselines. Tags enable you to categorize your resources in different ways,
+ *    for example, by purpose, owner, or environment. Each tag consists of a key and an optional value,
+ *    both of which you define. For example, you could define a set of tags for your account's managed
+ *    nodes that helps you track each node's owner and stack level. For example:</p>
  *          <ul>
  *             <li>
  *                <p>
@@ -60,7 +60,8 @@ export interface AddTagsToResourceCommandOutput extends AddTagsToResourceResult,
  *                </p>
  *             </li>
  *          </ul>
- *          <p>Most resources can have a maximum of 50 tags. Automations can have a maximum of 5 tags.</p>
+ *          <p>Most resources can have a maximum of 50 tags. Automations can have a maximum of 5
+ *    tags.</p>
  *          <p>We recommend that you devise a set of tag keys that meets your needs for each resource type.
  *    Using a consistent set of tag keys makes it easier for you to manage your resources. You can
  *    search and filter the resources based on the tags you add. Tags don't have any semantic meaning

clients/client-ssm/src/commands/GetMaintenanceWindowTaskCommand.ts

@@ -23,13 +23,13 @@ export interface GetMaintenanceWindowTaskCommandOutput extends GetMaintenanceWin
 
 /**
  * <p>Retrieves the details of a maintenance window task.</p>
- *  	       <note>
- *  		         <p>For maintenance window tasks without a specified target, you can't supply values for
- *  			<code>--max-errors</code> and <code>--max-concurrency</code>. Instead, the system inserts a
- *  			placeholder value of <code>1</code>, which may be reported in the response to this command.
- *  			These values don't affect the running of your task and can be ignored.</p>
- *  	       </note>
- *  	       <p>To retrieve a list of tasks in a maintenance window, instead use the <a>DescribeMaintenanceWindowTasks</a> command.</p>
+ *          <note>
+ *             <p>For maintenance window tasks without a specified target, you can't supply values for
+ *      <code>--max-errors</code> and <code>--max-concurrency</code>. Instead, the system inserts a
+ *     placeholder value of <code>1</code>, which may be reported in the response to this command.
+ *     These values don't affect the running of your task and can be ignored.</p>
+ *          </note>
+ *          <p>To retrieve a list of tasks in a maintenance window, instead use the <a>DescribeMaintenanceWindowTasks</a> command.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

clients/client-ssm/src/models/models_0.ts

@@ -1235,7 +1235,9 @@ export interface CreateAssociationRequest {
   /**
    * <p>Number of days to wait after the scheduled day to run an association. For example, if you
    *    specified a cron schedule of <code>cron(0 0 ? * THU#2 *)</code>, you could specify an offset of 3
-   *    to run the association each Sunday after the second Thursday of the month. For more information about cron schedules for associations, see <a href="https://docs.aws.amazon.com/systems-manager/latest/userguide/reference-cron-and-rate-expressions.html">Reference: Cron and rate expressions for Systems Manager</a> in the <i>Amazon Web Services Systems Manager User Guide</i>. </p>
+   *    to run the association each Sunday after the second Thursday of the month. For more information
+   *    about cron schedules for associations, see <a href="https://docs.aws.amazon.com/systems-manager/latest/userguide/reference-cron-and-rate-expressions.html">Reference: Cron
+   *     and rate expressions for Systems Manager</a> in the <i>Amazon Web Services Systems Manager User Guide</i>. </p>
    *          <note>
    *             <p>To use offsets, you must specify the <code>ApplyOnlyAtCronInterval</code> parameter. This
    *     option tells the system not to run an association immediately after you create it. </p>
@@ -5384,6 +5386,12 @@ export interface Runbook {
    */
   Targets?: Target[];
 
+  /**
+   * <p>A key-value mapping of runbook parameters to target resources. Both Targets and TargetMaps
+   *    can't be specified together.</p>
+   */
+  TargetMaps?: { [key: string]: string[] }[];
+
   /**
    * <p>The <code>MaxConcurrency</code> value specified by the user when the operation started,
    *    indicating the maximum number of resources that the runbook operation can run on at the same

clients/client-ssm/src/models/models_1.ts

@@ -1254,13 +1254,13 @@ export interface GetCommandInvocationRequest {
   InstanceId: string | undefined;
 
   /**
-   * <p>The name of the plugin for which you want detailed results. If the document contains only
-   *    one plugin, you can omit the name and details for that plugin. If the document contains more than
-   *    one plugin, you must specify the name of the plugin for which you want to view details.</p>
-   *          <p>Plugin names are also referred to as <i>step names</i> in Systems Manager documents (SSM
-   *    documents). For example, <code>aws:RunShellScript</code> is a plugin.</p>
+   * <p>The name of the step for which you want detailed results. If the document contains only one
+   *    step, you can omit the name and details for that step. If the document contains more than one
+   *    step, you must specify the name of the step for which you want to view details. Be sure to
+   *    specify the name of the step, not the name of a plugin like
+   *    <code>aws:RunShellScript</code>.</p>
    *          <p>To find the <code>PluginName</code>, check the document content and find the name of the
-   *    plugin. Alternatively, use <a>ListCommandInvocations</a> with the
+   *    step you want details for. Alternatively, use <a>ListCommandInvocations</a> with the
    *     <code>CommandId</code> and <code>Details</code> parameters. The <code>PluginName</code> is the
    *     <code>Name</code> attribute of the <code>CommandPlugin</code> object in the
    *     <code>CommandPlugins</code> list.</p>
@@ -10331,7 +10331,9 @@ export interface UpdateAssociationRequest {
   /**
    * <p>Number of days to wait after the scheduled day to run an association. For example, if you
    *    specified a cron schedule of <code>cron(0 0 ? * THU#2 *)</code>, you could specify an offset of 3
-   *    to run the association each Sunday after the second Thursday of the month. For more information about cron schedules for associations, see <a href="https://docs.aws.amazon.com/systems-manager/latest/userguide/reference-cron-and-rate-expressions.html">Reference: Cron and rate expressions for Systems Manager</a> in the <i>Amazon Web Services Systems Manager User Guide</i>. </p>
+   *    to run the association each Sunday after the second Thursday of the month. For more information
+   *    about cron schedules for associations, see <a href="https://docs.aws.amazon.com/systems-manager/latest/userguide/reference-cron-and-rate-expressions.html">Reference: Cron
+   *     and rate expressions for Systems Manager</a> in the <i>Amazon Web Services Systems Manager User Guide</i>. </p>
    *          <note>
    *             <p>To use offsets, you must specify the <code>ApplyOnlyAtCronInterval</code> parameter. This
    *     option tells the system not to run an association immediately after you create it. </p>

clients/client-ssm/src/protocols/Aws_json1_1.ts

@@ -14441,6 +14441,8 @@ const serializeAws_json1_1Runbook = (input: Runbook, context: __SerdeContext): a
       input.TargetLocations !== null && {
         TargetLocations: serializeAws_json1_1TargetLocations(input.TargetLocations, context),
       }),
+    ...(input.TargetMaps !== undefined &&
+      input.TargetMaps !== null && { TargetMaps: serializeAws_json1_1TargetMaps(input.TargetMaps, context) }),
     ...(input.TargetParameterName !== undefined &&
       input.TargetParameterName !== null && { TargetParameterName: input.TargetParameterName }),
     ...(input.Targets !== undefined &&
@@ -20676,6 +20678,10 @@ const deserializeAws_json1_1Runbook = (output: any, context: __SerdeContext): Ru
       output.TargetLocations !== undefined && output.TargetLocations !== null
         ? deserializeAws_json1_1TargetLocations(output.TargetLocations, context)
         : undefined,
+    TargetMaps:
+      output.TargetMaps !== undefined && output.TargetMaps !== null
+        ? deserializeAws_json1_1TargetMaps(output.TargetMaps, context)
+        : undefined,
     TargetParameterName: __expectString(output.TargetParameterName),
     Targets:
       output.Targets !== undefined && output.Targets !== null