docs(client-iot): Documentation update for China region ListMetricValues for IoT

Author: awstools

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

@@ -4746,6 +4746,11 @@ export interface CreateJobRequest {
    *             specified as targets have completed the job (SNAPSHOT). If continuous, the job may also be run on a thing
    *             when a change is detected in a target. For example, a job will run on a thing when the thing is added to a
    *             target group, even after the job was completed by all things originally in the group.</p>
+   *         <note>
+   *             <p>We recommend that you use continuous jobs instead of snapshot jobs for dynamic thing group targets.
+   *                 By using continuous jobs, devices that join the group receive the job execution even after the job has
+   *                 been created.</p>
+   *         </note>
    */
   targetSelection?: TargetSelection | string;
 
@@ -4796,7 +4801,13 @@ export interface CreateJobRequest {
   jobExecutionsRetryConfig?: JobExecutionsRetryConfig;
 
   /**
-   * <p>Parameters of a managed template that you can specify to create the job document.</p>
+   * <p>Parameters of an Amazon Web Services managed template that you can specify to create the job document.</p>
+   *         <note>
+   *             <p>
+   *                <code>documentParameters</code> can only be used when creating jobs from Amazon Web Services
+   *                 managed templates. This parameter can't be used with custom job templates or to
+   *                 create jobs from them.</p>
+   *         </note>
    */
   documentParameters?: { [key: string]: string };
 }
@@ -5506,12 +5517,12 @@ export interface CustomCodeSigning {
   certificateChain?: CodeSigningCertificateChain;
 
   /**
-   * <p>The hash algorithm used to code sign the file.</p>
+   * <p>The hash algorithm used to code sign the file. You can use a string as the algorithm name if the target over-the-air (OTA) update devices are able to verify the signature that was generated using the same signature algorithm. For example, FreeRTOS uses <code>SHA256</code> or <code>SHA1</code>, so you can pass either of them based on which was used for generating the signature.</p>
    */
   hashAlgorithm?: string;
 
   /**
-   * <p>The signature algorithm used to code sign the file.</p>
+   * <p>The signature algorithm used to code sign the file. You can use a string as the algorithm name if the target over-the-air (OTA) update devices are able to verify the signature that was generated using the same signature algorithm. For example, FreeRTOS uses <code>ECDSA</code> or <code>RSA</code>, so you can pass either of them based on which was used for generating the signature.</p>
    */
   signatureAlgorithm?: string;
 }

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

@@ -2078,6 +2078,11 @@ export interface Job {
    *             when a change is detected in a target. For example, a job will run on a device when the thing representing
    *             the device is added to a target group, even after the job was completed by all things originally in the
    *             group. </p>
+   *         <note>
+   *             <p>We recommend that you use continuous jobs instead of snapshot jobs for dynamic thing group targets.
+   *                 By using continuous jobs, devices that join the group receive the job execution even after the job has
+   *                 been created.</p>
+   *         </note>
    */
   targetSelection?: TargetSelection | string;
 
@@ -2183,6 +2188,12 @@ export interface Job {
    * <p>A key-value map that pairs the patterns that need to be replaced in a managed
    *             template job document schema. You can use the description of each key as a guidance
    *             to specify the inputs during runtime when creating a job.</p>
+   *         <note>
+   *             <p>
+   *                <code>documentParameters</code> can only be used when creating jobs from Amazon Web Services
+   *                 managed templates. This parameter can't be used with custom job templates or to
+   *                 create jobs from them.</p>
+   *         </note>
    */
   documentParameters?: { [key: string]: string };
 
@@ -2481,6 +2492,12 @@ export namespace DescribeManagedJobTemplateRequest {
  * <p>A map of key-value pairs containing the patterns that need to be replaced in a managed
  *             template job document schema. You can use the description of each key as a guidance to specify
  *             the inputs during runtime when creating a job.</p>
+ *         <note>
+ *             <p>
+ *                <code>documentParameters</code> can only be used when creating jobs from Amazon Web Services
+ *                 managed templates. This parameter can't be used with custom job templates or to
+ *                 create jobs from them.</p>
+ *         </note>
  */
 export interface DocumentParameter {
   /**
@@ -2552,6 +2569,12 @@ export interface DescribeManagedJobTemplateResponse {
   /**
    * <p>A map of key-value pairs that you can use as guidance to specify the inputs for creating
    *             a job from a managed template.</p>
+   *         <note>
+   *             <p>
+   *                <code>documentParameters</code> can only be used when creating jobs from Amazon Web Services
+   *                 managed templates. This parameter can't be used with custom job templates or to
+   *                 create jobs from them.</p>
+   *         </note>
    */
   documentParameters?: DocumentParameter[];
 
@@ -6611,6 +6634,11 @@ export interface ListJobsRequest {
    *             specified as targets have completed the job (SNAPSHOT). If continuous, the job may also be run on a thing
    *             when a change is detected in a target. For example, a job will run on a thing when the thing is added to a
    *             target group, even after the job was completed by all things originally in the group. </p>
+   *         <note>
+   *             <p>We recommend that you use continuous jobs instead of snapshot jobs for dynamic thing group targets.
+   *                 By using continuous jobs, devices that join the group receive the job execution even after the job has
+   *                 been created.</p>
+   *         </note>
    */
   targetSelection?: TargetSelection | string;
 
@@ -6681,6 +6709,11 @@ export interface JobSummary {
    *             specified as targets have completed the job (SNAPSHOT). If continuous, the job may also be run on a thing
    *             when a change is detected in a target. For example, a job will run on a thing when the thing is added to a
    *             target group, even after the job was completed by all things originally in the group.</p>
+   *         <note>
+   *             <p>We recommend that you use continuous jobs instead of snapshot jobs for dynamic thing group targets.
+   *                 By using continuous jobs, devices that join the group receive the job execution even after the job has
+   *                 been created.</p>
+   *         </note>
    */
   targetSelection?: TargetSelection | string;