Merge branch 'release-1.35.48'

* release-1.35.48:
  Bumping version to 1.35.48
  Update endpoints model
  Update to latest models
  Remove nimble client following the service deprecation

.changes/1.35.48.json

@@ -0,0 +1,32 @@
+[
+  {
+    "category": "``appconfig``",
+    "description": "This release improves deployment safety by granting customers the ability to REVERT completed deployments, to the last known good state.In the StopDeployment API revert case the status of a COMPLETE deployment will be REVERTED. AppConfig only allows a revert within 72 hours of deployment completion.",
+    "type": "api-change"
+  },
+  {
+    "category": "``ec2``",
+    "description": "This release includes a new API to describe some details of the Amazon Machine Images (AMIs) that were used to launch EC2 instances, even if those AMIs are no longer available for use.",
+    "type": "api-change"
+  },
+  {
+    "category": "``ecs``",
+    "description": "This release adds support for EBS volumes attached to Amazon ECS Windows tasks running on EC2 instances.",
+    "type": "api-change"
+  },
+  {
+    "category": "``nimble``",
+    "description": "The nimble client has been removed following the deprecation of the service.",
+    "type": "api-change"
+  },
+  {
+    "category": "``pcs``",
+    "description": "Documentation update: added the default value of the Slurm configuration parameter scaleDownIdleTimeInSeconds to its description.",
+    "type": "api-change"
+  },
+  {
+    "category": "``qbusiness``",
+    "description": "Add a new field in chat response. This field can be used to support nested schemas in array fields",
+    "type": "api-change"
+  }
+]

CHANGELOG.rst

@@ -2,6 +2,17 @@
 CHANGELOG
 =========
 
+1.35.48
+=======
+
+* api-change:``appconfig``: This release improves deployment safety by granting customers the ability to REVERT completed deployments, to the last known good state.In the StopDeployment API revert case the status of a COMPLETE deployment will be REVERTED. AppConfig only allows a revert within 72 hours of deployment completion.
+* api-change:``ec2``: This release includes a new API to describe some details of the Amazon Machine Images (AMIs) that were used to launch EC2 instances, even if those AMIs are no longer available for use.
+* api-change:``ecs``: This release adds support for EBS volumes attached to Amazon ECS Windows tasks running on EC2 instances.
+* api-change:``nimble``: The nimble client has been removed following the deprecation of the service.
+* api-change:``pcs``: Documentation update: added the default value of the Slurm configuration parameter scaleDownIdleTimeInSeconds to its description.
+* api-change:``qbusiness``: Add a new field in chat response. This field can be used to support nested schemas in array fields
+
+
 1.35.47
 =======
 

botocore/__init__.py

@@ -16,7 +16,7 @@
 import os
 import re
 
-__version__ = '1.35.47'
+__version__ = '1.35.48'
 
 
 class NullHandler(logging.Handler):

botocore/data/appconfig/2019-10-09/service-2.json

@@ -572,7 +572,7 @@
         {"shape":"InternalServerException"},
         {"shape":"BadRequestException"}
       ],
-      "documentation":"<p>Stops a deployment. This API action works only on deployments that have a status of <code>DEPLOYING</code>. This action moves the deployment to a status of <code>ROLLED_BACK</code>.</p>"
+      "documentation":"<p>Stops a deployment. This API action works only on deployments that have a status of <code>DEPLOYING</code>, unless an <code>AllowRevert</code> parameter is supplied. If the <code>AllowRevert</code> parameter is supplied, the status of an in-progress deployment will be <code>ROLLED_BACK</code>. The status of a completed deployment will be <code>REVERTED</code>. AppConfig only allows a revert within 72 hours of deployment completion.</p>"
     },
     "TagResource":{
       "name":"TagResource",
@@ -1609,7 +1609,8 @@
         "ROLLBACK_COMPLETED",
         "BAKE_TIME_STARTED",
         "DEPLOYMENT_STARTED",
-        "DEPLOYMENT_COMPLETED"
+        "DEPLOYMENT_COMPLETED",
+        "REVERT_COMPLETED"
       ]
     },
     "DeploymentEvents":{
@@ -1628,7 +1629,8 @@
         "DEPLOYING",
         "COMPLETE",
         "ROLLING_BACK",
-        "ROLLED_BACK"
+        "ROLLED_BACK",
+        "REVERTED"
       ]
     },
     "DeploymentStrategies":{
@@ -1811,7 +1813,8 @@
         "READY_FOR_DEPLOYMENT",
         "DEPLOYING",
         "ROLLING_BACK",
-        "ROLLED_BACK"
+        "ROLLED_BACK",
+        "REVERTED"
       ]
     },
     "Environments":{
@@ -2040,7 +2043,7 @@
         },
         "ClientConfigurationVersion":{
           "shape":"Version",
-          "documentation":"<p>The configuration version returned in the most recent <a>GetConfiguration</a> response.</p> <important> <p>AppConfig uses the value of the <code>ClientConfigurationVersion</code> parameter to identify the configuration version on your clients. If you don’t send <code>ClientConfigurationVersion</code> with each call to <a>GetConfiguration</a>, your clients receive the current configuration. You are charged each time your clients receive a configuration.</p> <p>To avoid excess charges, we recommend you use the <a href=\"https://docs.aws.amazon.com/appconfig/2019-10-09/APIReference/StartConfigurationSession.html\">StartConfigurationSession</a> and <a href=\"https://docs.aws.amazon.com/appconfig/2019-10-09/APIReference/GetLatestConfiguration.html\">GetLatestConfiguration</a> APIs, which track the client configuration version on your behalf. If you choose to continue using <a>GetConfiguration</a>, we recommend that you include the <code>ClientConfigurationVersion</code> value with every call to <a>GetConfiguration</a>. The value to use for <code>ClientConfigurationVersion</code> comes from the <code>ConfigurationVersion</code> attribute returned by <a>GetConfiguration</a> when there is new or updated data, and should be saved for subsequent calls to <a>GetConfiguration</a>.</p> </important> <p>For more information about working with configurations, see <a href=\"http://docs.aws.amazon.com/appconfig/latest/userguide/appconfig-retrieving-the-configuration.html\">Retrieving the Configuration</a> in the <i>AppConfig User Guide</i>.</p>",
+          "documentation":"<p>The configuration version returned in the most recent <a>GetConfiguration</a> response.</p> <important> <p>AppConfig uses the value of the <code>ClientConfigurationVersion</code> parameter to identify the configuration version on your clients. If you don’t send <code>ClientConfigurationVersion</code> with each call to <a>GetConfiguration</a>, your clients receive the current configuration. You are charged each time your clients receive a configuration.</p> <p>To avoid excess charges, we recommend you use the <a href=\"https://docs.aws.amazon.com/appconfig/2019-10-09/APIReference/StartConfigurationSession.html\">StartConfigurationSession</a> and <a href=\"https://docs.aws.amazon.com/appconfig/2019-10-09/APIReference/GetLatestConfiguration.html\">GetLatestConfiguration</a> APIs, which track the client configuration version on your behalf. If you choose to continue using <a>GetConfiguration</a>, we recommend that you include the <code>ClientConfigurationVersion</code> value with every call to <a>GetConfiguration</a>. The value to use for <code>ClientConfigurationVersion</code> comes from the <code>ConfigurationVersion</code> attribute returned by <a>GetConfiguration</a> when there is new or updated data, and should be saved for subsequent calls to <a>GetConfiguration</a>.</p> </important> <p>For more information about working with configurations, see <a href=\"http://docs.aws.amazon.com/appconfig/latest/userguide/retrieving-feature-flags.html\">Retrieving feature flags and configuration data in AppConfig</a> in the <i>AppConfig User Guide</i>.</p>",
           "location":"querystring",
           "locationName":"client_configuration_version"
         }
@@ -2804,6 +2807,13 @@
           "box":true,
           "location":"uri",
           "locationName":"DeploymentNumber"
+        },
+        "AllowRevert":{
+          "shape":"Boolean",
+          "documentation":"<p>A Boolean that enables AppConfig to rollback a <code>COMPLETED</code> deployment to the previous configuration version. This action moves the deployment to a status of <code>REVERTED</code>.</p>",
+          "box":true,
+          "location":"header",
+          "locationName":"Allow-Revert"
         }
       }
     },

botocore/data/ec2/2016-11-15/paginators-1.json

@@ -859,6 +859,12 @@
       "limit_key": "MaxResults",
       "output_token": "NextToken",
       "result_key": "CapacityReservationBillingRequests"
+    },
+    "DescribeInstanceImageMetadata": {
+      "input_token": "NextToken",
+      "limit_key": "MaxResults",
+      "output_token": "NextToken",
+      "result_key": "InstanceImageMetadata"
     }
   }
 }