Merge branch 'release-1.27.54' into develop

* release-1.27.54: Bumping version to 1.27.54 Update to latest models
boto · Aug 17, 2022 · 1504eb4 · 1504eb4
2 parents b6295d7 + 10802c2
commit 1504eb4
Show file tree

Hide file tree

Showing 12 changed files with 794 additions and 55 deletions.
diff --git a/.changes/1.27.54.json b/.changes/1.27.54.json
@@ -0,0 +1,42 @@
+[
+  {
+    "category": "``appmesh``",
+    "description": "AWS App Mesh release to support Multiple Listener and Access Log Format feature",
+    "type": "api-change"
+  },
+  {
+    "category": "``connectcampaigns``",
+    "description": "Updated exceptions for Amazon Connect Outbound Campaign api's.",
+    "type": "api-change"
+  },
+  {
+    "category": "``kendra``",
+    "description": "This release adds Zendesk connector (which allows you to specify Zendesk SAAS platform as data source), Proxy Support for Sharepoint and Confluence Server (which allows you to specify the proxy configuration if proxy is required to connect to your Sharepoint/Confluence Server as data source).",
+    "type": "api-change"
+  },
+  {
+    "category": "``lakeformation``",
+    "description": "This release adds a new API support \"AssumeDecoratedRoleWithSAML\" and also release updates the corresponding documentation.",
+    "type": "api-change"
+  },
+  {
+    "category": "``lambda``",
+    "description": "Added support for customization of Consumer Group ID for MSK and Kafka Event Source Mappings.",
+    "type": "api-change"
+  },
+  {
+    "category": "``lexv2-models``",
+    "description": "Update lexv2-models client to latest version",
+    "type": "api-change"
+  },
+  {
+    "category": "``rds``",
+    "description": "Adds support for Internet Protocol Version 6 (IPv6) for RDS Aurora database clusters.",
+    "type": "api-change"
+  },
+  {
+    "category": "``secretsmanager``",
+    "description": "Documentation updates for Secrets Manager.",
+    "type": "api-change"
+  }
+]
diff --git a/CHANGELOG.rst b/CHANGELOG.rst
@@ -2,6 +2,19 @@
 CHANGELOG
 =========
 
+1.27.54
+=======
+
+* api-change:``appmesh``: AWS App Mesh release to support Multiple Listener and Access Log Format feature
+* api-change:``connectcampaigns``: Updated exceptions for Amazon Connect Outbound Campaign api's.
+* api-change:``kendra``: This release adds Zendesk connector (which allows you to specify Zendesk SAAS platform as data source), Proxy Support for Sharepoint and Confluence Server (which allows you to specify the proxy configuration if proxy is required to connect to your Sharepoint/Confluence Server as data source).
+* api-change:``lakeformation``: This release adds a new API support "AssumeDecoratedRoleWithSAML" and also release updates the corresponding documentation.
+* api-change:``lambda``: Added support for customization of Consumer Group ID for MSK and Kafka Event Source Mappings.
+* api-change:``lexv2-models``: Update lexv2-models client to latest version
+* api-change:``rds``: Adds support for Internet Protocol Version 6 (IPv6) for RDS Aurora database clusters.
+* api-change:``secretsmanager``: Documentation updates for Secrets Manager.
+
+
 1.27.53
 =======
 

diff --git a/botocore/__init__.py b/botocore/__init__.py
@@ -16,7 +16,7 @@
 import os
 import re
 
-__version__ = '1.27.53'
+__version__ = '1.27.54'
 
 
 class NullHandler(logging.Handler):

diff --git a/botocore/data/appmesh/2019-01-25/service-2.json b/botocore/data/appmesh/2019-01-25/service-2.json
@@ -863,7 +863,7 @@
         },
         "ipPreference":{
           "shape":"IpPreference",
-          "documentation":"<p>The IP version to use to control traffic within the mesh.</p>"
+          "documentation":"<p>The preferred IP version that this virtual node uses. Setting the IP preference on the virtual node only overrides the IP preference set for the mesh on this specific node.</p>"
         },
         "namespaceName":{
           "shape":"AwsCloudMapName",
@@ -1922,7 +1922,7 @@
         },
         "ipPreference":{
           "shape":"IpPreference",
-          "documentation":"<p>The IP version to use to control traffic within the mesh.</p>"
+          "documentation":"<p>The preferred IP version that this virtual node uses. Setting the IP preference on the virtual node only overrides the IP preference set for the mesh on this specific node.</p>"
         },
         "responseType":{
           "shape":"DnsResponseType",
@@ -1984,6 +1984,10 @@
       "type":"structure",
       "required":["path"],
       "members":{
+        "format":{
+          "shape":"LoggingFormat",
+          "documentation":"<p>The specified format for the logs. The format is either <code>json_format</code> or <code>text_format</code>.</p>"
+        },
         "path":{
           "shape":"FilePath",
           "documentation":"<p>The file path to write access logs to. You can use <code>/dev/stdout</code> to send access logs to standard out and configure your Envoy container to use a log driver, such as <code>awslogs</code>, to export the access logs to a log storage service such as Amazon CloudWatch Logs. You can also specify a path in the Envoy container's file system to write the files to disk.</p> <pre><code> &lt;note&gt; &lt;p&gt;The Envoy process must have write permissions to the path that you specify here. Otherwise, Envoy fails to bootstrap properly.&lt;/p&gt; &lt;/note&gt; </code></pre>"
@@ -2175,6 +2179,10 @@
       "type":"structure",
       "required":["virtualService"],
       "members":{
+        "port":{
+          "shape":"ListenerPort",
+          "documentation":"<p>The port number of the gateway route target.</p>"
+        },
         "virtualService":{
           "shape":"GatewayRouteVirtualService",
           "documentation":"<p>An object that represents a virtual service gateway route target.</p>"
@@ -2237,6 +2245,10 @@
           "shape":"GrpcGatewayRouteMetadataList",
           "documentation":"<p>The gateway route metadata to be matched on.</p>"
         },
+        "port":{
+          "shape":"ListenerPort",
+          "documentation":"<p>The port number to match from the request.</p>"
+        },
         "serviceName":{
           "shape":"ServiceName",
           "documentation":"<p>The fully qualified domain name for the service to match from the request.</p>"
@@ -2397,6 +2409,10 @@
           "shape":"MethodName",
           "documentation":"<p>The method name to match from the request. If you specify a name, you must also specify a <code>serviceName</code>.</p>"
         },
+        "port":{
+          "shape":"ListenerPort",
+          "documentation":"<p>The port number to match on.</p>"
+        },
         "serviceName":{
           "shape":"ServiceName",
           "documentation":"<p>The fully qualified domain name for the service to match from the request.</p>"
@@ -2643,6 +2659,10 @@
           "shape":"HttpPathMatch",
           "documentation":"<p>The path to match on.</p>"
         },
+        "port":{
+          "shape":"ListenerPort",
+          "documentation":"<p>The port number to match on.</p>"
+        },
         "prefix":{
           "shape":"String",
           "documentation":"<p>Specifies the path to match requests with. This parameter must always start with <code>/</code>, which by itself matches all requests to the virtual service name. You can also match for path-based routing of requests. For example, if your virtual service name is <code>my-service.local</code> and you want the route to match requests to <code>my-service.local/metrics</code>, your prefix should be <code>/metrics</code>.</p>"
@@ -2874,6 +2894,10 @@
           "shape":"HttpPathMatch",
           "documentation":"<p>The client request path to match on.</p>"
         },
+        "port":{
+          "shape":"ListenerPort",
+          "documentation":"<p>The port number to match on.</p>"
+        },
         "prefix":{
           "shape":"String",
           "documentation":"<p>Specifies the path to match requests with. This parameter must always start with <code>/</code>, which by itself matches all requests to the virtual service name. You can also match for path-based routing of requests. For example, if your virtual service name is <code>my-service.local</code> and you want the route to match requests to <code>my-service.local/metrics</code>, your prefix should be <code>/metrics</code>.</p>"
@@ -2930,6 +2954,38 @@
         "IPv6_ONLY"
       ]
     },
+    "JsonFormat":{
+      "type":"list",
+      "member":{"shape":"JsonFormatRef"}
+    },
+    "JsonFormatRef":{
+      "type":"structure",
+      "required":[
+        "key",
+        "value"
+      ],
+      "members":{
+        "key":{
+          "shape":"JsonKey",
+          "documentation":"<p>The specified key for the JSON.</p>"
+        },
+        "value":{
+          "shape":"JsonValue",
+          "documentation":"<p>The specified value for the JSON.</p>"
+        }
+      },
+      "documentation":"<p>An object that represents the key value pairs for the JSON.</p>"
+    },
+    "JsonKey":{
+      "type":"string",
+      "max":100,
+      "min":1
+    },
+    "JsonValue":{
+      "type":"string",
+      "max":100,
+      "min":1
+    },
     "LimitExceededException":{
       "type":"structure",
       "members":{
@@ -3378,6 +3434,12 @@
       },
       "documentation":"<p>An object that represents a listener for a virtual node.</p>"
     },
+    "ListenerPort":{
+      "type":"integer",
+      "box":true,
+      "max":65535,
+      "min":1
+    },
     "ListenerTimeout":{
       "type":"structure",
       "members":{
@@ -3534,6 +3596,21 @@
       },
       "documentation":"<p>An object that represents the logging information for a virtual node.</p>"
     },
+    "LoggingFormat":{
+      "type":"structure",
+      "members":{
+        "json":{
+          "shape":"JsonFormat",
+          "documentation":"<p/>"
+        },
+        "text":{
+          "shape":"TextFormat",
+          "documentation":"<p/>"
+        }
+      },
+      "documentation":"<p>An object that represents the format for the logs.</p>",
+      "union":true
+    },
     "Long":{
       "type":"long",
       "box":true
@@ -4156,6 +4233,10 @@
           "shape":"TcpRouteAction",
           "documentation":"<p>The action to take if a match is determined.</p>"
         },
+        "match":{
+          "shape":"TcpRouteMatch",
+          "documentation":"<p>An object that represents the criteria for determining a request match.</p>"
+        },
         "timeout":{
           "shape":"TcpTimeout",
           "documentation":"<p>An object that represents types of timeouts. </p>"
@@ -4174,6 +4255,16 @@
       },
       "documentation":"<p>An object that represents the action to take if a match is determined.</p>"
     },
+    "TcpRouteMatch":{
+      "type":"structure",
+      "members":{
+        "port":{
+          "shape":"ListenerPort",
+          "documentation":"<p>The port number to match on.</p>"
+        }
+      },
+      "documentation":"<p>An object representing the TCP route to match.</p>"
+    },
     "TcpTimeout":{
       "type":"structure",
       "members":{
@@ -4184,14 +4275,19 @@
       },
       "documentation":"<p>An object that represents types of timeouts. </p>"
     },
+    "TextFormat":{
+      "type":"string",
+      "max":1000,
+      "min":1
+    },
     "Timestamp":{"type":"timestamp"},
     "TlsValidationContext":{
       "type":"structure",
       "required":["trust"],
       "members":{
         "subjectAlternativeNames":{
           "shape":"SubjectAlternativeNames",
-          "documentation":"<p>A reference to an object that represents the SANs for a Transport Layer Security (TLS) validation context.</p>"
+          "documentation":"<p>A reference to an object that represents the SANs for a Transport Layer Security (TLS) validation context. If you don't specify SANs on the <i>terminating</i> mesh endpoint, the Envoy proxy for that node doesn't verify the SAN on a peer client certificate. If you don't specify SANs on the <i>originating</i> mesh endpoint, the SAN on the certificate provided by the terminating endpoint must match the mesh endpoint service discovery configuration. Since SPIRE vended certificates have a SPIFFE ID as a name, you must set the SAN since the name doesn't match the service discovery name.</p>"
         },
         "trust":{
           "shape":"TlsValidationContextTrust",
@@ -4773,6 +4869,10 @@
       "type":"structure",
       "required":["path"],
       "members":{
+        "format":{
+          "shape":"LoggingFormat",
+          "documentation":"<p>The specified format for the virtual gateway access logs. It can be either <code>json_format</code> or <code>text_format</code>.</p>"
+        },
         "path":{
           "shape":"FilePath",
           "documentation":"<p>The file path to write access logs to. You can use <code>/dev/stdout</code> to send access logs to standard out and configure your Envoy container to use a log driver, such as <code>awslogs</code>, to export the access logs to a log storage service such as Amazon CloudWatch Logs. You can also specify a path in the Envoy container's file system to write the files to disk.</p>"
@@ -5711,6 +5811,10 @@
         "weight"
       ],
       "members":{
+        "port":{
+          "shape":"ListenerPort",
+          "documentation":"<p>The targeted port of the weighted object.</p>"
+        },
         "virtualNode":{
           "shape":"ResourceName",
           "documentation":"<p>The virtual node to associate with the weighted target.</p>"

diff --git a/botocore/data/connectcampaigns/2021-01-30/service-2.json b/botocore/data/connectcampaigns/2021-01-30/service-2.json
@@ -116,6 +116,7 @@
       "errors":[
         {"shape":"InternalServerException"},
         {"shape":"ResourceNotFoundException"},
+        {"shape":"ValidationException"},
         {"shape":"AccessDeniedException"},
         {"shape":"ThrottlingException"}
       ],
@@ -218,6 +219,7 @@
       "errors":[
         {"shape":"InternalServerException"},
         {"shape":"ResourceNotFoundException"},
+        {"shape":"ValidationException"},
         {"shape":"ConflictException"},
         {"shape":"InvalidCampaignStateException"},
         {"shape":"AccessDeniedException"},
@@ -257,6 +259,7 @@
       "errors":[
         {"shape":"InternalServerException"},
         {"shape":"ResourceNotFoundException"},
+        {"shape":"ValidationException"},
         {"shape":"ConflictException"},
         {"shape":"InvalidCampaignStateException"},
         {"shape":"AccessDeniedException"},
@@ -275,6 +278,7 @@
       "errors":[
         {"shape":"InternalServerException"},
         {"shape":"ResourceNotFoundException"},
+        {"shape":"ValidationException"},
         {"shape":"ConflictException"},
         {"shape":"InvalidCampaignStateException"},
         {"shape":"AccessDeniedException"},
@@ -313,6 +317,7 @@
       "errors":[
         {"shape":"InternalServerException"},
         {"shape":"ResourceNotFoundException"},
+        {"shape":"ValidationException"},
         {"shape":"ConflictException"},
         {"shape":"InvalidCampaignStateException"},
         {"shape":"AccessDeniedException"},