Merge branch 'release-1.42.76' into develop

* release-1.42.76:
  Bumping version to 1.42.76
  Update to latest models

Author: aws-sdk-python-automation

.changes/1.42.76.json

@@ -0,0 +1,37 @@
+[
+  {
+    "category": "``apigatewayv2``",
+    "description": "Added DISABLE IN PROGRESS and DISABLE FAILED Portal statuses.",
+    "type": "api-change"
+  },
+  {
+    "category": "``application-signals``",
+    "description": "This release adds support for creating SLOs on RUM appMonitors, Synthetics canaries and services.",
+    "type": "api-change"
+  },
+  {
+    "category": "``batch``",
+    "description": "Documentation-only update for AWS Batch.",
+    "type": "api-change"
+  },
+  {
+    "category": "``endpoint-rules``",
+    "description": "Update endpoint-rules client to latest version",
+    "type": "api-change"
+  },
+  {
+    "category": "``marketplace-agreement``",
+    "description": "The Variable Payments APIs enable AWS Marketplace Sellers to perform manage their payment requests (send, get, list, cancel).",
+    "type": "api-change"
+  },
+  {
+    "category": "``polly``",
+    "description": "Add support for Mu-law and A-law codecs for output format",
+    "type": "api-change"
+  },
+  {
+    "category": "``uxc``",
+    "description": "GA release of AccountCustomizations, used to manage account color, visible services, and visible regions settings in the AWS Management Console.",
+    "type": "api-change"
+  }
+]

CHANGELOG.rst

@@ -2,6 +2,18 @@
 CHANGELOG
 =========
 
+1.42.76
+=======
+
+* api-change:``apigatewayv2``: Added DISABLE IN PROGRESS and DISABLE FAILED Portal statuses.
+* api-change:``application-signals``: This release adds support for creating SLOs on RUM appMonitors, Synthetics canaries and services.
+* api-change:``batch``: Documentation-only update for AWS Batch.
+* api-change:``endpoint-rules``: Update endpoint-rules client to latest version
+* api-change:``marketplace-agreement``: The Variable Payments APIs enable AWS Marketplace Sellers to perform manage their payment requests (send, get, list, cancel).
+* api-change:``polly``: Add support for Mu-law and A-law codecs for output format
+* api-change:``uxc``: GA release of AccountCustomizations, used to manage account color, visible services, and visible regions settings in the AWS Management Console.
+
+
 1.42.75
 =======
 

botocore/__init__.py

@@ -17,7 +17,7 @@
 import re
 from logging import NullHandler
 
-__version__ = '1.42.75'
+__version__ = '1.42.76'
 
 
 # Configure default logger to do nothing

botocore/data/apigatewayv2/2018-11-29/service-2.json

@@ -10364,6 +10364,8 @@
         "PUBLISHED",
         "PUBLISH_IN_PROGRESS",
         "PUBLISH_FAILED",
+        "DISABLE_IN_PROGRESS",
+        "DISABLE_FAILED",
         "DISABLED"
       ]
     },

botocore/data/application-signals/2024-04-15/service-2.json

@@ -1671,6 +1671,10 @@
           "location":"querystring",
           "locationName":"NextToken"
         },
+        "MetricSourceTypes":{
+          "shape":"MetricSourceTypes",
+          "documentation":"<p>Use this optional field to only include SLOs with the specified metric source types in the output. Supported types are:</p> <ul> <li> <p>Service operation</p> </li> <li> <p>Service dependency</p> </li> <li> <p>Service</p> </li> <li> <p>CloudWatch metric</p> </li> <li> <p>AppMonitor</p> </li> <li> <p>Canary</p> </li> </ul>"
+        },
         "IncludeLinkedAccounts":{
           "shape":"Boolean",
           "documentation":"<p>If you are using this operation in a monitoring account, specify <code>true</code> to include SLO from source accounts in the returned data. </p> <p>When you are monitoring an account, you can use Amazon Web Services account ID in <code>KeyAttribute</code> filter for service source account and <code>SloOwnerawsaccountID</code> for SLO source account with <code>IncludeLinkedAccounts</code> to filter the returned data to only a single source account. </p>",
@@ -1683,9 +1687,9 @@
           "location":"querystring",
           "locationName":"SloOwnerAwsAccountId"
         },
-        "MetricSourceTypes":{
-          "shape":"MetricSourceTypes",
-          "documentation":"<p>Use this optional field to only include SLOs with the specified metric source types in the output. Supported types are:</p> <ul> <li> <p>Service operation</p> </li> <li> <p>Service dependency</p> </li> <li> <p>CloudWatch metric</p> </li> </ul>"
+        "MetricSource":{
+          "shape":"MetricSource",
+          "documentation":"<p>Identifies the metric source to filter SLOs by.</p>"
         }
       }
     },
@@ -2074,12 +2078,30 @@
       "type":"list",
       "member":{"shape":"MetricReference"}
     },
+    "MetricSource":{
+      "type":"structure",
+      "required":["MetricSourceKeyAttributes"],
+      "members":{
+        "MetricSourceKeyAttributes":{
+          "shape":"Attributes",
+          "documentation":"<p>Key attributes that identify the metric source.</p>"
+        },
+        "MetricSourceAttributes":{
+          "shape":"Attributes",
+          "documentation":"<p>Additional attributes for the metric source.</p>"
+        }
+      },
+      "documentation":"<p>Identifies the metric source for SLOs on resources other than Application Signals services.</p>"
+    },
     "MetricSourceType":{
       "type":"string",
       "enum":[
         "ServiceOperation",
         "CloudWatchMetric",
-        "ServiceDependency"
+        "ServiceDependency",
+        "AppMonitor",
+        "Canary",
+        "Service"
       ]
     },
     "MetricSourceTypes":{
@@ -2295,6 +2317,10 @@
         "DependencyConfig":{
           "shape":"DependencyConfig",
           "documentation":"<p>Identifies the dependency using the <code>DependencyKeyAttributes</code> and <code>DependencyOperationName</code>. </p>"
+        },
+        "MetricSource":{
+          "shape":"MetricSource",
+          "documentation":"<p>Identifies the metric source for SLOs on resources other than Application Signals services.</p>"
         }
       },
       "documentation":"<p>This structure contains the information about the metric that is used for a request-based SLO.</p>"
@@ -2325,6 +2351,14 @@
         "DependencyConfig":{
           "shape":"DependencyConfig",
           "documentation":"<p>Identifies the dependency using the <code>DependencyKeyAttributes</code> and <code>DependencyOperationName</code>. </p>"
+        },
+        "MetricSource":{
+          "shape":"MetricSource",
+          "documentation":"<p>Identifies the metric source for SLOs on resources other than Application Signals services.</p>"
+        },
+        "MetricName":{
+          "shape":"MetricName",
+          "documentation":"<p>The name of the metric for SLOs on resources other than Application Signals services.</p>"
         }
       },
       "documentation":"<p>Use this structure to specify the information for the metric that a period-based SLO will monitor.</p>"
@@ -2618,6 +2652,10 @@
         "DependencyConfig":{
           "shape":"DependencyConfig",
           "documentation":"<p>Identifies the dependency using the <code>DependencyKeyAttributes</code> and <code>DependencyOperationName</code>. </p>"
+        },
+        "MetricSource":{
+          "shape":"MetricSource",
+          "documentation":"<p>Identifies the metric source for SLOs on resources other than Application Signals services.</p>"
         }
       },
       "documentation":"<p>This structure contains the information about the metric that is used for a period-based SLO.</p>"
@@ -2649,6 +2687,10 @@
           "shape":"SLIPeriodSeconds",
           "documentation":"<p>The number of seconds to use as the period for SLO evaluation. Your application's performance is compared to the SLI during each period. For each period, the application is determined to have either achieved or not achieved the necessary performance.</p>"
         },
+        "MetricSource":{
+          "shape":"MetricSource",
+          "documentation":"<p>Identifies the metric source for SLOs on resources other than Application Signals services.</p>"
+        },
         "MetricDataQueries":{
           "shape":"MetricDataQueries",
           "documentation":"<p>If this SLO monitors a CloudWatch metric or the result of a CloudWatch metric math expression, use this structure to specify that metric or expression. </p>"
@@ -2726,7 +2768,7 @@
         },
         "MetricSourceType":{
           "shape":"MetricSourceType",
-          "documentation":"<p>Displays the SLI metric source type for this SLO. Supported types are:</p> <ul> <li> <p>Service operation</p> </li> <li> <p>Service dependency</p> </li> <li> <p>CloudWatch metric</p> </li> </ul>"
+          "documentation":"<p>Displays the SLI metric source type for this SLO. Supported types are:</p> <ul> <li> <p>Service operation</p> </li> <li> <p>Service dependency</p> </li> <li> <p>Service</p> </li> <li> <p>CloudWatch metric</p> </li> <li> <p>AppMonitor</p> </li> <li> <p>Canary</p> </li> </ul>"
         }
       },
       "documentation":"<p>A structure containing information about one service level objective (SLO) that has been created in Application Signals. Creating SLOs can help you ensure your services are performing to the level that you expect. SLOs help you set and track a specific target level for the reliability and availability of your applications and services. Each SLO uses a service level indicator (SLI), which is a key performance metric, to calculate how much underperformance can be tolerated before the goal that you set for the SLO is not achieved.</p>"
@@ -2915,7 +2957,11 @@
         },
         "MetricSourceType":{
           "shape":"MetricSourceType",
-          "documentation":"<p>Displays the SLI metric source type for this SLO. Supported types are:</p> <ul> <li> <p>Service operation</p> </li> <li> <p>Service dependency</p> </li> <li> <p>CloudWatch metric</p> </li> </ul>"
+          "documentation":"<p>Displays the SLI metric source type for this SLO. Supported types are:</p> <ul> <li> <p>Service operation</p> </li> <li> <p>Service dependency</p> </li> <li> <p>Service</p> </li> <li> <p>CloudWatch metric</p> </li> <li> <p>AppMonitor</p> </li> <li> <p>Canary</p> </li> </ul>"
+        },
+        "MetricSource":{
+          "shape":"MetricSource",
+          "documentation":"<p>Identifies the metric source for SLOs on resources other than Application Signals services.</p>"
         }
       },
       "documentation":"<p>A structure that contains information about one service level objective (SLO) created in Application Signals.</p>"

botocore/data/application-signals/2024-04-15/waiters-2.json

@@ -0,0 +1,5 @@
+{
+  "version": 2,
+  "waiters": {
+  }
+}

botocore/data/batch/2016-08-10/service-2.json

@@ -4360,7 +4360,7 @@
         },
         "jobStatus":{
           "shape":"ServiceJobStatus",
-          "documentation":"<p>The job status used to filter service jobs in the specified queue. If the <code>filters</code> parameter is specified, the <code>jobStatus</code> parameter is ignored and jobs with any status are returned. The exception is the <code>SHARE_IDENTIFIER</code> filter and <code>jobStatus</code> can be used together. If you don't specify a status, only <code>RUNNING</code> jobs are returned.</p> <note> <p>The <code>SHARE_IDENTIFIER</code> filter and the <code>jobStatus</code> field can be used together to filter results.</p> </note>"
+          "documentation":"<p>The job status used to filter service jobs in the specified queue. If the <code>filters</code> parameter is specified, the <code>jobStatus</code> parameter is ignored and jobs with any status are returned. The exceptions are the <code>SHARE_IDENTIFIER</code> filter and <code>QUOTA_SHARE_NAME</code> filter, which can be used with <code>jobStatus</code>. If you don't specify a status, only <code>RUNNING</code> jobs are returned.</p> <note> <p>The <code>SHARE_IDENTIFIER</code> filter or <code>QUOTA_SHARE_NAME</code> filter can be used with the <code>jobStatus</code> field to filter results.</p> </note>"
         },
         "maxResults":{
           "shape":"Integer",
@@ -4372,7 +4372,7 @@
         },
         "filters":{
           "shape":"ListJobsFilterList",
-          "documentation":"<p>The filter to apply to the query. Only one filter can be used at a time. When the filter is used, <code>jobStatus</code> is ignored with the exception that <code>SHARE_IDENTIFIER</code> and <code>jobStatus</code> can be used together. The results are sorted by the <code>createdAt</code> field, with the most recent jobs being first.</p> <note> <p>The <code>SHARE_IDENTIFIER</code> filter and the <code>jobStatus</code> field can be used together to filter results.</p> </note> <dl> <dt>JOB_NAME</dt> <dd> <p>The value of the filter is a case-insensitive match for the job name. If the value ends with an asterisk (*), the filter matches any job name that begins with the string before the '*'. This corresponds to the <code>jobName</code> value. For example, <code>test1</code> matches both <code>Test1</code> and <code>test1</code>, and <code>test1*</code> matches both <code>test1</code> and <code>Test10</code>. When the <code>JOB_NAME</code> filter is used, the results are grouped by the job name and version.</p> </dd> <dt>BEFORE_CREATED_AT</dt> <dd> <p>The value for the filter is the time that's before the job was created. This corresponds to the <code>createdAt</code> value. The value is a string representation of the number of milliseconds since 00:00:00 UTC (midnight) on January 1, 1970.</p> </dd> <dt>AFTER_CREATED_AT</dt> <dd> <p>The value for the filter is the time that's after the job was created. This corresponds to the <code>createdAt</code> value. The value is a string representation of the number of milliseconds since 00:00:00 UTC (midnight) on January 1, 1970.</p> </dd> <dt>SHARE_IDENTIFIER</dt> <dd> <p>The value for the filter is the fairshare scheduling share identifier.</p> </dd> </dl>"
+          "documentation":"<p>The filter to apply to the query. Only one filter can be used at a time. When the filter is used, <code>jobStatus</code> is ignored with the exception that <code>SHARE_IDENTIFIER</code> or <code>QUOTA_SHARE_NAME</code> and <code>jobStatus</code> can be used together. The results are sorted by the <code>createdAt</code> field, with the most recent jobs being first.</p> <note> <p>The <code>SHARE_IDENTIFIER</code> or <code>QUOTA_SHARE_NAME</code> filter and the <code>jobStatus</code> field can be used together to filter results.</p> </note> <dl> <dt>JOB_NAME</dt> <dd> <p>The value of the filter is a case-insensitive match for the job name. If the value ends with an asterisk (*), the filter matches any job name that begins with the string before the '*'. This corresponds to the <code>jobName</code> value. For example, <code>test1</code> matches both <code>Test1</code> and <code>test1</code>, and <code>test1*</code> matches both <code>test1</code> and <code>Test10</code>. When the <code>JOB_NAME</code> filter is used, the results are grouped by the job name and version.</p> </dd> <dt>BEFORE_CREATED_AT</dt> <dd> <p>The value for the filter is the time that's before the job was created. This corresponds to the <code>createdAt</code> value. The value is a string representation of the number of milliseconds since 00:00:00 UTC (midnight) on January 1, 1970.</p> </dd> <dt>AFTER_CREATED_AT</dt> <dd> <p>The value for the filter is the time that's after the job was created. This corresponds to the <code>createdAt</code> value. The value is a string representation of the number of milliseconds since 00:00:00 UTC (midnight) on January 1, 1970.</p> </dd> <dt>SHARE_IDENTIFIER</dt> <dd> <p>The value for the filter is the fairshare scheduling share identifier.</p> </dd> <dt>QUOTA_SHARE_NAME</dt> <dd> <p>The value for the filter is the quota management share name.</p> </dd> </dl>"
         }
       }
     },

botocore/data/marketplace-agreement/2020-03-01/paginators-1.json

@@ -1,3 +1,10 @@
 {
-  "pagination": {}
+  "pagination": {
+    "ListAgreementPaymentRequests": {
+      "input_token": "nextToken",
+      "output_token": "nextToken",
+      "limit_key": "maxResults",
+      "result_key": "items"
+    }
+  }
 }