Skip to content

Commit

Permalink
Update to latest models
Browse files Browse the repository at this point in the history
  • Loading branch information
aws-sdk-python-automation committed Jul 30, 2024
1 parent 7c2bffa commit 793b3b9
Show file tree
Hide file tree
Showing 26 changed files with 1,531 additions and 1,628 deletions.
5 changes: 5 additions & 0 deletions .changes/next-release/api-change-appstream-47667.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"type": "api-change",
"category": "``appstream``",
"description": "Added support for Red Hat Enterprise Linux 8 on Amazon AppStream 2.0"
}
5 changes: 5 additions & 0 deletions .changes/next-release/api-change-autoscaling-65241.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"type": "api-change",
"category": "``autoscaling``",
"description": "Increase the length limit for VPCZoneIdentifier from 2047 to 5000"
}
5 changes: 5 additions & 0 deletions .changes/next-release/api-change-codepipeline-45681.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"type": "api-change",
"category": "``codepipeline``",
"description": "AWS CodePipeline V2 type pipelines now support stage level conditions to enable development teams to safely release changes that meet quality and compliance requirements."
}
5 changes: 5 additions & 0 deletions .changes/next-release/api-change-elasticache-8326.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"type": "api-change",
"category": "``elasticache``",
"description": "Doc only update for changes to deletion API."
}
5 changes: 5 additions & 0 deletions .changes/next-release/api-change-elb-16161.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"type": "api-change",
"category": "``elb``",
"description": "Add v2 smoke tests and smithy smokeTests trait for SDK testing."
}
5 changes: 5 additions & 0 deletions .changes/next-release/api-change-events-78682.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"type": "api-change",
"category": "``events``",
"description": "Add v2 smoke tests and smithy smokeTests trait for SDK testing."
}
5 changes: 5 additions & 0 deletions .changes/next-release/api-change-lexv2models-71003.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"type": "api-change",
"category": "``lexv2-models``",
"description": "This release adds new capabilities to the AMAZON.QnAIntent: Custom prompting, Guardrails integration and ExactResponse support for Bedrock Knowledge Base."
}
5 changes: 5 additions & 0 deletions .changes/next-release/api-change-logs-80944.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"type": "api-change",
"category": "``logs``",
"description": "Add v2 smoke tests and smithy smokeTests trait for SDK testing."
}
5 changes: 5 additions & 0 deletions .changes/next-release/api-change-rolesanywhere-66026.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"type": "api-change",
"category": "``rolesanywhere``",
"description": "IAM RolesAnywhere now supports custom role session name on the CreateSession. This release adds the acceptRoleSessionName option to a profile to control whether a role session name will be accepted in a session request with a given profile."
}
5 changes: 5 additions & 0 deletions .changes/next-release/api-change-tnb-44823.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"type": "api-change",
"category": "``tnb``",
"description": "This release adds Network Service Update, through which customers will be able to update their instantiated networks to a new network package. See the documentation for limitations. The release also enhances the Get network operation API to return parameter overrides used during the operation."
}
5 changes: 5 additions & 0 deletions .changes/next-release/api-change-workspaces-87080.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"type": "api-change",
"category": "``workspaces``",
"description": "Removing multi-session as it isn't supported for pools"
}
21 changes: 12 additions & 9 deletions botocore/data/appstream/2016-12-01/service-2.json
Original file line number Diff line number Diff line change
Expand Up @@ -5,12 +5,14 @@
"endpointPrefix":"appstream2",
"jsonVersion":"1.1",
"protocol":"json",
"protocols":["json"],
"serviceFullName":"Amazon AppStream",
"serviceId":"AppStream",
"signatureVersion":"v4",
"signingName":"appstream",
"targetPrefix":"PhotonAdminProxyService",
"uid":"appstream-2016-12-01"
"uid":"appstream-2016-12-01",
"auth":["aws.auth#sigv4"]
},
"operations":{
"AssociateAppBlockBuilderAppBlock":{
Expand Down Expand Up @@ -2189,7 +2191,7 @@
},
"DisconnectTimeoutInSeconds":{
"shape":"Integer",
"documentation":"<p>The amount of time that a streaming session remains active after users disconnect. If users try to reconnect to the streaming session after a disconnection or network interruption within this time interval, they are connected to their previous session. Otherwise, they are connected to a new session with a new streaming instance. </p> <p>Specify a value between 60 and 360000.</p>"
"documentation":"<p>The amount of time that a streaming session remains active after users disconnect. If users try to reconnect to the streaming session after a disconnection or network interruption within this time interval, they are connected to their previous session. Otherwise, they are connected to a new session with a new streaming instance. </p> <p>Specify a value between 60 and 36000.</p>"
},
"Description":{
"shape":"Description",
Expand All @@ -2213,7 +2215,7 @@
},
"IdleDisconnectTimeoutInSeconds":{
"shape":"Integer",
"documentation":"<p>The amount of time that users can be idle (inactive) before they are disconnected from their streaming session and the <code>DisconnectTimeoutInSeconds</code> time interval begins. Users are notified before they are disconnected due to inactivity. If they try to reconnect to the streaming session before the time interval specified in <code>DisconnectTimeoutInSeconds</code> elapses, they are connected to their previous session. Users are considered idle when they stop providing keyboard or mouse input during their streaming session. File uploads and downloads, audio in, audio out, and pixels changing do not qualify as user activity. If users continue to be idle after the time interval in <code>IdleDisconnectTimeoutInSeconds</code> elapses, they are disconnected.</p> <p>To prevent users from being disconnected due to inactivity, specify a value of 0. Otherwise, specify a value between 60 and 3600. The default value is 0.</p> <note> <p>If you enable this feature, we recommend that you specify a value that corresponds exactly to a whole number of minutes (for example, 60, 120, and 180). If you don't do this, the value is rounded to the nearest minute. For example, if you specify a value of 70, users are disconnected after 1 minute of inactivity. If you specify a value that is at the midpoint between two different minutes, the value is rounded up. For example, if you specify a value of 90, users are disconnected after 2 minutes of inactivity. </p> </note>"
"documentation":"<p>The amount of time that users can be idle (inactive) before they are disconnected from their streaming session and the <code>DisconnectTimeoutInSeconds</code> time interval begins. Users are notified before they are disconnected due to inactivity. If they try to reconnect to the streaming session before the time interval specified in <code>DisconnectTimeoutInSeconds</code> elapses, they are connected to their previous session. Users are considered idle when they stop providing keyboard or mouse input during their streaming session. File uploads and downloads, audio in, audio out, and pixels changing do not qualify as user activity. If users continue to be idle after the time interval in <code>IdleDisconnectTimeoutInSeconds</code> elapses, they are disconnected.</p> <p>To prevent users from being disconnected due to inactivity, specify a value of 0. Otherwise, specify a value between 60 and 36000. The default value is 0.</p> <note> <p>If you enable this feature, we recommend that you specify a value that corresponds exactly to a whole number of minutes (for example, 60, 120, and 180). If you don't do this, the value is rounded to the nearest minute. For example, if you specify a value of 70, users are disconnected after 1 minute of inactivity. If you specify a value that is at the midpoint between two different minutes, the value is rounded up. For example, if you specify a value of 90, users are disconnected after 2 minutes of inactivity. </p> </note>"
},
"IamRoleArn":{
"shape":"Arn",
Expand Down Expand Up @@ -3702,7 +3704,7 @@
},
"DisconnectTimeoutInSeconds":{
"shape":"Integer",
"documentation":"<p>The amount of time that a streaming session remains active after users disconnect. If they try to reconnect to the streaming session after a disconnection or network interruption within this time interval, they are connected to their previous session. Otherwise, they are connected to a new session with a new streaming instance.</p> <p>Specify a value between 60 and 360000.</p>"
"documentation":"<p>The amount of time that a streaming session remains active after users disconnect. If they try to reconnect to the streaming session after a disconnection or network interruption within this time interval, they are connected to their previous session. Otherwise, they are connected to a new session with a new streaming instance.</p> <p>Specify a value between 60 and 36000.</p>"
},
"State":{
"shape":"FleetState",
Expand Down Expand Up @@ -3730,7 +3732,7 @@
},
"IdleDisconnectTimeoutInSeconds":{
"shape":"Integer",
"documentation":"<p>The amount of time that users can be idle (inactive) before they are disconnected from their streaming session and the <code>DisconnectTimeoutInSeconds</code> time interval begins. Users are notified before they are disconnected due to inactivity. If users try to reconnect to the streaming session before the time interval specified in <code>DisconnectTimeoutInSeconds</code> elapses, they are connected to their previous session. Users are considered idle when they stop providing keyboard or mouse input during their streaming session. File uploads and downloads, audio in, audio out, and pixels changing do not qualify as user activity. If users continue to be idle after the time interval in <code>IdleDisconnectTimeoutInSeconds</code> elapses, they are disconnected.</p> <p>To prevent users from being disconnected due to inactivity, specify a value of 0. Otherwise, specify a value between 60 and 3600. The default value is 0.</p> <note> <p>If you enable this feature, we recommend that you specify a value that corresponds exactly to a whole number of minutes (for example, 60, 120, and 180). If you don't do this, the value is rounded to the nearest minute. For example, if you specify a value of 70, users are disconnected after 1 minute of inactivity. If you specify a value that is at the midpoint between two different minutes, the value is rounded up. For example, if you specify a value of 90, users are disconnected after 2 minutes of inactivity. </p> </note>"
"documentation":"<p>The amount of time that users can be idle (inactive) before they are disconnected from their streaming session and the <code>DisconnectTimeoutInSeconds</code> time interval begins. Users are notified before they are disconnected due to inactivity. If users try to reconnect to the streaming session before the time interval specified in <code>DisconnectTimeoutInSeconds</code> elapses, they are connected to their previous session. Users are considered idle when they stop providing keyboard or mouse input during their streaming session. File uploads and downloads, audio in, audio out, and pixels changing do not qualify as user activity. If users continue to be idle after the time interval in <code>IdleDisconnectTimeoutInSeconds</code> elapses, they are disconnected.</p> <p>To prevent users from being disconnected due to inactivity, specify a value of 0. Otherwise, specify a value between 60 and 36000. The default value is 0.</p> <note> <p>If you enable this feature, we recommend that you specify a value that corresponds exactly to a whole number of minutes (for example, 60, 120, and 180). If you don't do this, the value is rounded to the nearest minute. For example, if you specify a value of 70, users are disconnected after 1 minute of inactivity. If you specify a value that is at the midpoint between two different minutes, the value is rounded up. For example, if you specify a value of 90, users are disconnected after 2 minutes of inactivity. </p> </note>"
},
"IamRoleArn":{
"shape":"Arn",
Expand Down Expand Up @@ -4344,7 +4346,8 @@
"WINDOWS_SERVER_2016",
"WINDOWS_SERVER_2019",
"WINDOWS_SERVER_2022",
"AMAZON_LINUX2"
"AMAZON_LINUX2",
"RHEL8"
]
},
"Platforms":{
Expand Down Expand Up @@ -5177,7 +5180,7 @@
},
"DisconnectTimeoutInSeconds":{
"shape":"Integer",
"documentation":"<p>The amount of time that a streaming session remains active after users disconnect. If users try to reconnect to the streaming session after a disconnection or network interruption within this time interval, they are connected to their previous session. Otherwise, they are connected to a new session with a new streaming instance. </p> <p>Specify a value between 60 and 360000.</p>"
"documentation":"<p>The amount of time that a streaming session remains active after users disconnect. If users try to reconnect to the streaming session after a disconnection or network interruption within this time interval, they are connected to their previous session. Otherwise, they are connected to a new session with a new streaming instance. </p> <p>Specify a value between 60 and 36000.</p>"
},
"DeleteVpcConfig":{
"shape":"Boolean",
Expand All @@ -5202,7 +5205,7 @@
},
"IdleDisconnectTimeoutInSeconds":{
"shape":"Integer",
"documentation":"<p>The amount of time that users can be idle (inactive) before they are disconnected from their streaming session and the <code>DisconnectTimeoutInSeconds</code> time interval begins. Users are notified before they are disconnected due to inactivity. If users try to reconnect to the streaming session before the time interval specified in <code>DisconnectTimeoutInSeconds</code> elapses, they are connected to their previous session. Users are considered idle when they stop providing keyboard or mouse input during their streaming session. File uploads and downloads, audio in, audio out, and pixels changing do not qualify as user activity. If users continue to be idle after the time interval in <code>IdleDisconnectTimeoutInSeconds</code> elapses, they are disconnected. </p> <p>To prevent users from being disconnected due to inactivity, specify a value of 0. Otherwise, specify a value between 60 and 3600. The default value is 0.</p> <note> <p>If you enable this feature, we recommend that you specify a value that corresponds exactly to a whole number of minutes (for example, 60, 120, and 180). If you don't do this, the value is rounded to the nearest minute. For example, if you specify a value of 70, users are disconnected after 1 minute of inactivity. If you specify a value that is at the midpoint between two different minutes, the value is rounded up. For example, if you specify a value of 90, users are disconnected after 2 minutes of inactivity. </p> </note>"
"documentation":"<p>The amount of time that users can be idle (inactive) before they are disconnected from their streaming session and the <code>DisconnectTimeoutInSeconds</code> time interval begins. Users are notified before they are disconnected due to inactivity. If users try to reconnect to the streaming session before the time interval specified in <code>DisconnectTimeoutInSeconds</code> elapses, they are connected to their previous session. Users are considered idle when they stop providing keyboard or mouse input during their streaming session. File uploads and downloads, audio in, audio out, and pixels changing do not qualify as user activity. If users continue to be idle after the time interval in <code>IdleDisconnectTimeoutInSeconds</code> elapses, they are disconnected. </p> <p>To prevent users from being disconnected due to inactivity, specify a value of 0. Otherwise, specify a value between 60 and 36000. The default value is 0.</p> <note> <p>If you enable this feature, we recommend that you specify a value that corresponds exactly to a whole number of minutes (for example, 60, 120, and 180). If you don't do this, the value is rounded to the nearest minute. For example, if you specify a value of 70, users are disconnected after 1 minute of inactivity. If you specify a value that is at the midpoint between two different minutes, the value is rounded up. For example, if you specify a value of 90, users are disconnected after 2 minutes of inactivity. </p> </note>"
},
"AttributesToDelete":{
"shape":"FleetAttributes",
Expand Down Expand Up @@ -5461,7 +5464,7 @@
},
"MaximumLength":{
"shape":"Integer",
"documentation":"<p>Specifies the number of characters that can be copied by end users from the local device to the remote session, and to the local device from the remote session.</p> <p>This can be specified only for the <code>CLIPBOARD_COPY_FROM_LOCAL_DEVICE</code> and <code>CLIPBOARD_COPY_TO_LOCAL_DEVICE</code> actions.</p> <p>This defaults to 20,971,520 (20 MB) when unspecified and the permission is <code>ENABLED</code>. This can't be specified when the permission is <code>DISABLED</code>. </p> <p>This can only be specified for AlwaysOn and OnDemand fleets. The attribute is not supported on Elastic fleets.</p> <p>The value can be between 1 and 20,971,520 (20 MB).</p>"
"documentation":"<p>Specifies the number of characters that can be copied by end users from the local device to the remote session, and to the local device from the remote session.</p> <p>This can be specified only for the <code>CLIPBOARD_COPY_FROM_LOCAL_DEVICE</code> and <code>CLIPBOARD_COPY_TO_LOCAL_DEVICE</code> actions.</p> <p>This defaults to 20,971,520 (20 MB) when unspecified and the permission is <code>ENABLED</code>. This can't be specified when the permission is <code>DISABLED</code>. </p> <p>The value can be between 1 and 20,971,520 (20 MB).</p>"
}
},
"documentation":"<p>Describes an action and whether the action is enabled or disabled for users during their streaming sessions.</p>"
Expand Down
12 changes: 9 additions & 3 deletions botocore/data/autoscaling/2011-01-01/service-2.json
Original file line number Diff line number Diff line change
Expand Up @@ -1459,7 +1459,7 @@
"documentation":"<p>The name of the placement group into which to launch your instances, if any.</p>"
},
"VPCZoneIdentifier":{
"shape":"XmlStringMaxLen2047",
"shape":"XmlStringMaxLen5000",
"documentation":"<p>One or more subnet IDs, if applicable, separated by commas.</p>"
},
"EnabledMetrics":{
Expand Down Expand Up @@ -1956,7 +1956,7 @@
"documentation":"<p>The name of the placement group into which to launch your instances. For more information, see <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/placement-groups.html\">Placement groups</a> in the <i>Amazon EC2 User Guide for Linux Instances</i>.</p> <note> <p>A <i>cluster</i> placement group is a logical grouping of instances within a single Availability Zone. You cannot specify multiple Availability Zones and a cluster placement group. </p> </note>"
},
"VPCZoneIdentifier":{
"shape":"XmlStringMaxLen2047",
"shape":"XmlStringMaxLen5000",
"documentation":"<p>A comma-separated list of subnet IDs for a virtual private cloud (VPC) where instances in the Auto Scaling group can be created. If you specify <code>VPCZoneIdentifier</code> with <code>AvailabilityZones</code>, the subnets that you specify must reside in those Availability Zones.</p>"
},
"TerminationPolicies":{
Expand Down Expand Up @@ -5609,7 +5609,7 @@
"documentation":"<p>The name of an existing placement group into which to launch your instances. For more information, see <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/placement-groups.html\">Placement groups</a> in the <i>Amazon EC2 User Guide for Linux Instances</i>.</p> <note> <p>A <i>cluster</i> placement group is a logical grouping of instances within a single Availability Zone. You cannot specify multiple Availability Zones and a cluster placement group. </p> </note>"
},
"VPCZoneIdentifier":{
"shape":"XmlStringMaxLen2047",
"shape":"XmlStringMaxLen5000",
"documentation":"<p>A comma-separated list of subnet IDs for a virtual private cloud (VPC). If you specify <code>VPCZoneIdentifier</code> with <code>AvailabilityZones</code>, the subnets that you specify must reside in those Availability Zones.</p>"
},
"TerminationPolicies":{
Expand Down Expand Up @@ -5752,6 +5752,12 @@
"min":1,
"pattern":"[\\u0020-\\uD7FF\\uE000-\\uFFFD\\uD800\\uDC00-\\uDBFF\\uDFFF\\r\\n\\t]*"
},
"XmlStringMaxLen5000":{
"type":"string",
"max":5000,
"min":1,
"pattern":"[\\u0020-\\uD7FF\\uE000-\\uFFFD\\uD800\\uDC00-\\uDBFF\\uDFFF\\r\\n\\t]*"
},
"XmlStringMaxLen511":{
"type":"string",
"max":511,
Expand Down
6 changes: 6 additions & 0 deletions botocore/data/codepipeline/2015-07-09/paginators-1.json
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,12 @@
"output_token": "nextToken",
"limit_key": "maxResults",
"result_key": "tags"
},
"ListRuleExecutions": {
"input_token": "nextToken",
"output_token": "nextToken",
"limit_key": "maxResults",
"result_key": "ruleExecutionDetails"
}
}
}
Loading

0 comments on commit 793b3b9

Please sign in to comment.