Skip to content

Commit

Permalink
Merge branch 'release-1.29.73' into develop
Browse files Browse the repository at this point in the history
* release-1.29.73:
  Bumping version to 1.29.73
  Update to latest partitions and endpoints
  Update to latest models
  • Loading branch information
aws-sdk-python-automation committed Feb 16, 2023
2 parents 2df8ee0 + e5628be commit 5de7254
Show file tree
Hide file tree
Showing 15 changed files with 1,427 additions and 2,316 deletions.
22 changes: 22 additions & 0 deletions .changes/1.29.73.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
[
{
"category": "``emr``",
"description": "Update emr client to latest version",
"type": "api-change"
},
{
"category": "``grafana``",
"description": "With this release Amazon Managed Grafana now supports inbound Network Access Control that helps you to restrict user access to your Grafana workspaces",
"type": "api-change"
},
{
"category": "``ivs``",
"description": "Doc-only update. Updated text description in DeleteChannel, Stream, and StreamSummary.",
"type": "api-change"
},
{
"category": "``wafv2``",
"description": "Added a notice for account takeover prevention (ATP). The interface incorrectly lets you to configure ATP response inspection in regional web ACLs in Region US East (N. Virginia), without returning an error. ATP response inspection is only available in web ACLs that protect CloudFront distributions.",
"type": "api-change"
}
]
9 changes: 9 additions & 0 deletions CHANGELOG.rst
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,15 @@
CHANGELOG
=========

1.29.73
=======

* api-change:``emr``: Update emr client to latest version
* api-change:``grafana``: With this release Amazon Managed Grafana now supports inbound Network Access Control that helps you to restrict user access to your Grafana workspaces
* api-change:``ivs``: Doc-only update. Updated text description in DeleteChannel, Stream, and StreamSummary.
* api-change:``wafv2``: Added a notice for account takeover prevention (ATP). The interface incorrectly lets you to configure ATP response inspection in regional web ACLs in Region US East (N. Virginia), without returning an error. ATP response inspection is only available in web ACLs that protect CloudFront distributions.


1.29.72
=======

Expand Down
2 changes: 1 addition & 1 deletion botocore/__init__.py
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
import os
import re

__version__ = '1.29.72'
__version__ = '1.29.73'


class NullHandler(logging.Handler):
Expand Down
412 changes: 228 additions & 184 deletions botocore/data/emr/2009-03-31/endpoint-rule-set-1.json

Large diffs are not rendered by default.

58 changes: 53 additions & 5 deletions botocore/data/emr/2009-03-31/service-2.json
Original file line number Diff line number Diff line change
Expand Up @@ -296,7 +296,7 @@
{"shape":"InternalServerError"},
{"shape":"InvalidRequestException"}
],
"documentation":"<p>Provides Temporary, basic HTTP credentials that are associated with a given runtime IAM role and used by a cluster with fine-grained access control activated. You can use these credentials to connect to cluster endpoints that support username-based and password-based authentication.</p>"
"documentation":"<p>Provides temporary, HTTP basic credentials that are associated with a given runtime IAM role and used by a cluster with fine-grained access control activated. You can use these credentials to connect to cluster endpoints that support username and password authentication.</p>"
},
"GetManagedScalingPolicy":{
"name":"GetManagedScalingPolicy",
Expand Down Expand Up @@ -2124,7 +2124,7 @@
"members":{
"Credentials":{
"shape":"Credentials",
"documentation":"<p>The credentials that you can use to connect to cluster endpoints that support username-based and password-based authentication.</p>"
"documentation":"<p>The credentials that you can use to connect to cluster endpoints that support username and password authentication.</p>"
},
"ExpiresAt":{
"shape":"Date",
Expand Down Expand Up @@ -2340,6 +2340,10 @@
"LaunchSpecifications":{
"shape":"InstanceFleetProvisioningSpecifications",
"documentation":"<p>Describes the launch specification for an instance fleet. </p>"
},
"ResizeSpecifications":{
"shape":"InstanceFleetResizingSpecifications",
"documentation":"<p>The resize specification for the instance fleet.</p>"
}
},
"documentation":"<p>Describes an instance fleet, which is a group of EC2 instances that host a particular node type (master, core, or task) in an Amazon EMR cluster. Instance fleets can consist of a mix of instance types and On-Demand and Spot Instances, which are provisioned to meet a defined target capacity. </p> <note> <p>The instance fleet configuration is available only in Amazon EMR versions 4.8.0 and later, excluding 5.0.x versions.</p> </note>"
Expand Down Expand Up @@ -2371,6 +2375,10 @@
"LaunchSpecifications":{
"shape":"InstanceFleetProvisioningSpecifications",
"documentation":"<p>The launch specification for the instance fleet.</p>"
},
"ResizeSpecifications":{
"shape":"InstanceFleetResizingSpecifications",
"documentation":"<p>The resize specification for the instance fleet.</p>"
}
},
"documentation":"<p>The configuration that defines an instance fleet.</p> <note> <p>The instance fleet configuration is available only in Amazon EMR versions 4.8.0 and later, excluding 5.0.x versions.</p> </note>"
Expand Down Expand Up @@ -2399,6 +2407,10 @@
"TargetSpotCapacity":{
"shape":"WholeNumber",
"documentation":"<p>The target capacity of Spot units for the instance fleet. For more information, see <a>InstanceFleetConfig$TargetSpotCapacity</a>.</p>"
},
"ResizeSpecifications":{
"shape":"InstanceFleetResizingSpecifications",
"documentation":"<p>The resize specification for the instance fleet.</p>"
}
},
"documentation":"<p>Configuration parameters for an instance fleet modification request.</p> <note> <p>The instance fleet configuration is available only in Amazon EMR versions 4.8.0 and later, excluding 5.0.x versions.</p> </note>"
Expand All @@ -2408,14 +2420,28 @@
"members":{
"SpotSpecification":{
"shape":"SpotProvisioningSpecification",
"documentation":"<p>The launch specification for Spot Instances in the fleet, which determines the defined duration, provisioning timeout behavior, and allocation strategy.</p>"
"documentation":"<p>The launch specification for Spot instances in the fleet, which determines the defined duration, provisioning timeout behavior, and allocation strategy.</p>"
},
"OnDemandSpecification":{
"shape":"OnDemandProvisioningSpecification",
"documentation":"<p> The launch specification for On-Demand Instances in the instance fleet, which determines the allocation strategy. </p> <note> <p>The instance fleet configuration is available only in Amazon EMR versions 4.8.0 and later, excluding 5.0.x versions. On-Demand Instances allocation strategy is available in Amazon EMR version 5.12.1 and later.</p> </note>"
}
},
"documentation":"<p>The launch specification for Spot Instances in the fleet, which determines the defined duration, provisioning timeout behavior, and allocation strategy.</p> <note> <p>The instance fleet configuration is available only in Amazon EMR versions 4.8.0 and later, excluding 5.0.x versions. On-Demand and Spot Instance allocation strategies are available in Amazon EMR version 5.12.1 and later.</p> </note>"
"documentation":"<p>The launch specification for Spot Instances in the fleet, which determines the defined duration, provisioning timeout behavior, and allocation strategy.</p> <note> <p>The instance fleet configuration is available only in Amazon EMR versions 4.8.0 and later, excluding 5.0.x versions. On-Demand and Spot instance allocation strategies are available in Amazon EMR version 5.12.1 and later.</p> </note>"
},
"InstanceFleetResizingSpecifications":{
"type":"structure",
"members":{
"SpotResizeSpecification":{
"shape":"SpotResizingSpecification",
"documentation":"<p>The resize specification for Spot Instances in the instance fleet, which contains the resize timeout period. </p>"
},
"OnDemandResizeSpecification":{
"shape":"OnDemandResizingSpecification",
"documentation":"<p>The resize specification for On-Demand Instances in the instance fleet, which contains the resize timeout period. </p>"
}
},
"documentation":"<p>The resize specification for On-Demand and Spot Instances in the fleet.</p>"
},
"InstanceFleetState":{
"type":"string",
Expand Down Expand Up @@ -4001,6 +4027,17 @@
},
"documentation":"<p> The launch specification for On-Demand Instances in the instance fleet, which determines the allocation strategy. </p> <note> <p>The instance fleet configuration is available only in Amazon EMR versions 4.8.0 and later, excluding 5.0.x versions. On-Demand Instances allocation strategy is available in Amazon EMR version 5.12.1 and later.</p> </note>"
},
"OnDemandResizingSpecification":{
"type":"structure",
"required":["TimeoutDurationMinutes"],
"members":{
"TimeoutDurationMinutes":{
"shape":"WholeNumber",
"documentation":"<p>On-Demand resize timeout in minutes. If On-Demand Instances are not provisioned within this time, the resize workflow stops. The minimum value is 5 minutes, and the maximum value is 10,080 minutes (7 days). The timeout applies to all resize workflows on the Instance Fleet. The resize could be triggered by Amazon EMR Managed Scaling or by the customer (via Amazon EMR Console, Amazon EMR CLI modify-instance-fleet or Amazon EMR SDK ModifyInstanceFleet API) or by Amazon EMR due to Amazon EC2 Spot Reclamation.</p>"
}
},
"documentation":"<p>The resize specification for On-Demand Instances in the instance fleet, which contains the resize timeout period. </p>"
},
"OptionalArnType":{
"type":"string",
"max":2048,
Expand Down Expand Up @@ -4700,7 +4737,7 @@
"members":{
"TimeoutDurationMinutes":{
"shape":"WholeNumber",
"documentation":"<p>The spot provisioning timeout period in minutes. If Spot Instances are not provisioned within this time period, the <code>TimeOutAction</code> is taken. Minimum value is 5 and maximum value is 1440. The timeout applies only during initial provisioning, when the cluster is first created.</p>"
"documentation":"<p>The Spot provisioning timeout period in minutes. If Spot Instances are not provisioned within this time period, the <code>TimeOutAction</code> is taken. Minimum value is 5 and maximum value is 1440. The timeout applies only during initial provisioning, when the cluster is first created.</p>"
},
"TimeoutAction":{
"shape":"SpotProvisioningTimeoutAction",
Expand All @@ -4724,6 +4761,17 @@
"TERMINATE_CLUSTER"
]
},
"SpotResizingSpecification":{
"type":"structure",
"required":["TimeoutDurationMinutes"],
"members":{
"TimeoutDurationMinutes":{
"shape":"WholeNumber",
"documentation":"<p>Spot resize timeout in minutes. If Spot Instances are not provisioned within this time, the resize workflow will stop provisioning of Spot instances. Minimum value is 5 minutes and maximum value is 10,080 minutes (7 days). The timeout applies to all resize workflows on the Instance Fleet. The resize could be triggered by Amazon EMR Managed Scaling or by the customer (via Amazon EMR Console, Amazon EMR CLI modify-instance-fleet or Amazon EMR SDK ModifyInstanceFleet API) or by Amazon EMR due to Amazon EC2 Spot Reclamation.</p>"
}
},
"documentation":"<p>The resize specification for Spot Instances in the instance fleet, which contains the resize timeout period. </p>"
},
"StartNotebookExecutionInput":{
"type":"structure",
"required":[
Expand Down
12 changes: 12 additions & 0 deletions botocore/data/endpoints.json
Original file line number Diff line number Diff line change
Expand Up @@ -2249,6 +2249,11 @@
},
"cases" : {
"endpoints" : {
"ap-southeast-1" : { },
"ap-southeast-2" : { },
"ca-central-1" : { },
"eu-central-1" : { },
"eu-west-2" : { },
"fips-us-east-1" : {
"deprecated" : true
},
Expand Down Expand Up @@ -8284,12 +8289,18 @@
"ap-east-1" : {
"hostname" : "kendra-ranking.ap-east-1.api.aws"
},
"ap-northeast-1" : {
"hostname" : "kendra-ranking.ap-northeast-1.api.aws"
},
"ap-northeast-2" : {
"hostname" : "kendra-ranking.ap-northeast-2.api.aws"
},
"ap-northeast-3" : {
"hostname" : "kendra-ranking.ap-northeast-3.api.aws"
},
"ap-south-1" : {
"hostname" : "kendra-ranking.ap-south-1.api.aws"
},
"ap-south-2" : {
"hostname" : "kendra-ranking.ap-south-2.api.aws"
},
Expand Down Expand Up @@ -11419,6 +11430,7 @@
"ap-southeast-1" : { },
"ap-southeast-2" : { },
"ap-southeast-3" : { },
"ap-southeast-4" : { },
"ca-central-1" : {
"variants" : [ {
"hostname" : "ram-fips.ca-central-1.amazonaws.com",
Expand Down
Loading

0 comments on commit 5de7254

Please sign in to comment.