Merge branch 'release-1.35.10' into develop

* release-1.35.10:
  Bumping version to 1.35.10
  Update endpoints model
  Update to latest models

.changes/1.35.10.json

@@ -0,0 +1,22 @@
+[
+  {
+    "category": "``backup``",
+    "description": "The latest update introduces two new attributes, VaultType and VaultState, to the DescribeBackupVault and ListBackupVaults APIs. The VaultState attribute reflects the current status of the vault, while the VaultType attribute indicates the specific category of the vault.",
+    "type": "api-change"
+  },
+  {
+    "category": "``datazone``",
+    "description": "Amazon DataZone now adds new governance capabilities of Domain Units for organization within your Data Domains, and Authorization Policies for tighter controls.",
+    "type": "api-change"
+  },
+  {
+    "category": "``logs``",
+    "description": "This release introduces a new optional parameter: Entity, in PutLogEvents request",
+    "type": "api-change"
+  },
+  {
+    "category": "``redshift-data``",
+    "description": "The release include the new Redshift DataAPI feature for session use, customer execute query with --session-keep-alive-seconds parameter and can submit follow-up queries to same sessions with returned`session-id`",
+    "type": "api-change"
+  }
+]

CHANGELOG.rst

@@ -2,6 +2,15 @@
 CHANGELOG
 =========
 
+1.35.10
+=======
+
+* api-change:``backup``: The latest update introduces two new attributes, VaultType and VaultState, to the DescribeBackupVault and ListBackupVaults APIs. The VaultState attribute reflects the current status of the vault, while the VaultType attribute indicates the specific category of the vault.
+* api-change:``datazone``: Amazon DataZone now adds new governance capabilities of Domain Units for organization within your Data Domains, and Authorization Policies for tighter controls.
+* api-change:``logs``: This release introduces a new optional parameter: Entity, in PutLogEvents request
+* api-change:``redshift-data``: The release include the new Redshift DataAPI feature for session use, customer execute query with --session-keep-alive-seconds parameter and can submit follow-up queries to same sessions with returned`session-id`
+
+
 1.35.9
 ======
 

botocore/__init__.py

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

botocore/data/datazone/2018-05-10/paginators-1.json

@@ -161,6 +161,24 @@
       "output_token": "nextToken",
       "limit_key": "maxResults",
       "result_key": "items"
+    },
+    "ListDomainUnitsForParent": {
+      "input_token": "nextToken",
+      "output_token": "nextToken",
+      "limit_key": "maxResults",
+      "result_key": "items"
+    },
+    "ListEntityOwners": {
+      "input_token": "nextToken",
+      "output_token": "nextToken",
+      "limit_key": "maxResults",
+      "result_key": "owners"
+    },
+    "ListPolicyGrants": {
+      "input_token": "nextToken",
+      "output_token": "nextToken",
+      "limit_key": "maxResults",
+      "result_key": "grantList"
     }
   }
 }