Merge branch 'release-1.17.111'

* release-1.17.111:
  Bumping version to 1.17.111
  Add changelog entries from botocore
  Typo fixes (#2916)

Author: aws-sdk-python-automation

.changes/1.17.111.json

@@ -0,0 +1,32 @@
+[
+  {
+    "category": "``amplifybackend``", 
+    "description": "[``botocore``] Added Sign in with Apple OAuth provider.", 
+    "type": "api-change"
+  }, 
+  {
+    "category": "``redshift``", 
+    "description": "[``botocore``] Release new APIs to support new Redshift feature - Authentication Profile", 
+    "type": "api-change"
+  }, 
+  {
+    "category": "``ssm``", 
+    "description": "[``botocore``] Changes to OpsCenter APIs to support a new feature, operational insights.", 
+    "type": "api-change"
+  }, 
+  {
+    "category": "``lex-models``", 
+    "description": "[``botocore``] Customers can now migrate bots built with Lex V1 APIs to V2 APIs. This release adds APIs to initiate and manage the migration of a bot.", 
+    "type": "api-change"
+  }, 
+  {
+    "category": "``directconnect``", 
+    "description": "[``botocore``] This release adds a new filed named awsLogicalDeviceId that it displays the AWS Direct Connect endpoint which terminates a physical connection's BGP Sessions.", 
+    "type": "api-change"
+  }, 
+  {
+    "category": "``pricing``", 
+    "description": "[``botocore``] Documentation updates for api.pricing", 
+    "type": "api-change"
+  }
+]

CHANGELOG.rst

@@ -2,6 +2,17 @@
 CHANGELOG
 =========
 
+1.17.111
+========
+
+* api-change:``amplifybackend``: [``botocore``] Added Sign in with Apple OAuth provider.
+* api-change:``redshift``: [``botocore``] Release new APIs to support new Redshift feature - Authentication Profile
+* api-change:``ssm``: [``botocore``] Changes to OpsCenter APIs to support a new feature, operational insights.
+* api-change:``lex-models``: [``botocore``] Customers can now migrate bots built with Lex V1 APIs to V2 APIs. This release adds APIs to initiate and manage the migration of a bot.
+* api-change:``directconnect``: [``botocore``] This release adds a new filed named awsLogicalDeviceId that it displays the AWS Direct Connect endpoint which terminates a physical connection's BGP Sessions.
+* api-change:``pricing``: [``botocore``] Documentation updates for api.pricing
+
+
 1.17.110
 ========
 

boto3/__init__.py

@@ -18,7 +18,7 @@
 
 
 __author__ = 'Amazon Web Services'
-__version__ = '1.17.110'
+__version__ = '1.17.111'
 
 
 # The default Boto3 session; autoloaded when needed.

docs/source/guide/cloud9.rst

@@ -34,7 +34,7 @@ in the *AWS Cloud9 User Guide*.
 Step 2: Create an environment
 -----------------------------
 After you sign in to the AWS Cloud9 console, use the console to 
-create an AWS Cloud9 development environment. (A *development environment* is 
+create an AWS Cloud9 development environment. (A *development environment* 
 is a place where you store your project's files and where you run the tools 
 to develop your apps.) After you create 
 the environment, AWS Cloud9 automatically opens the IDE for that environment.

docs/source/guide/credentials.rst

@@ -98,7 +98,7 @@ The shared credentials file has a default location of ``~/.aws/credentials``. Yo
 
 This file is an INI formatted file with section names corresponding to profiles. With each section, the three configuration variables shown above can be specified: ``aws_access_key_id``, ``aws_secret_access_key``, ``aws_session_token``. *These are the only supported values in the shared credential file.*
 
-Below is an minimal example of the shared credentials file:
+Below is a minimal example of the shared credentials file:
 
 .. code-block:: ini
 

docs/source/guide/cw-example-subscription-filters.rst

@@ -59,7 +59,7 @@ Prerequisite tasks
 
   Use the following role policy when creating the IAM role.
 
- .. code-block::  python
+ .. code-block:: python
    
         {
            "Version": "2012-10-17",

docs/source/guide/cw-example-using-alarms.rst

@@ -54,7 +54,7 @@ Prerequisite tasks
 
   Use the following role policy when creating the IAM role.
 
- .. code-block::  python
+ .. code-block:: python
 
         {
            "Version": "2012-10-17",

docs/source/guide/events.rst

@@ -46,7 +46,7 @@ Here is an example of how the event system works::
 
 In this example, the handler ``add_my_bucket``
 is registered such that the handler will inject the
-value ``'mybucket`` for the ``Bucket`` parameter whenever the the
+value ``'mybucket`` for the ``Bucket`` parameter whenever the
 ``list_objects`` client call is made without the ``Bucket`` parameter. Note
 that if the same ``list_objects`` call is made without the ``Bucket``
 parameter and the registered handler, it will result in a validation error.
@@ -58,7 +58,7 @@ Here are the takeaways from this example:
   ``meta.events`` attribute on the client.
 * All functions registered to the event system must have ``**kwargs`` in
   the function signature. This is because emitting an event can have any
-  number of keyword arguments emitted along side it, and so if your
+  number of keyword arguments emitted alongside it, and so if your
   function is called without ``**kwargs``, its signature will have to
   match every keyword argument emitted by the event. This also allows for
   more keyword arguments to be added to the emitted event in the future

docs/source/guide/resources.rst

@@ -184,7 +184,7 @@ exist without a bucket, these are parent to child relationships.
 
 Waiters
 -------
-A waiter is similiar to an action. A waiter will poll the status of a
+A waiter is similar to an action. A waiter will poll the status of a
 resource and suspend execution until the resource reaches the state that is
 being polled for or a failure occurs while polling.
 Waiters automatically set the resource

scripts/new-change

@@ -29,7 +29,7 @@ You'll see this template::
 Fill in the appropriate values, save and exit the editor.
 Make sure to commit these changes as part of your pull request.
 
-If, when your editor is open, you decide don't don't want to add a changelog
+If, when your editor is open, you decide don't want to add a changelog
 entry, save an empty file and no entry will be generated.
 
 You can then use the ``scripts/gen-changelog`` to generate the

setup.cfg

@@ -3,6 +3,6 @@ universal = 1
 
 [metadata]
 requires_dist =
-    botocore>=1.20.110,<1.21.0
+    botocore>=1.20.111,<1.21.0
     jmespath>=0.7.1,<1.0.0
     s3transfer>=0.4.0,<0.5.0

setup.py

@@ -14,7 +14,7 @@
 
 
 requires = [
-    'botocore>=1.20.110,<1.21.0',
+    'botocore>=1.20.111,<1.21.0',
     'jmespath>=0.7.1,<1.0.0',
     's3transfer>=0.4.0,<0.5.0'
 ]