Skip to content

Commit

Permalink
Merge branch 'release-1.35.39' into develop
Browse files Browse the repository at this point in the history
* release-1.35.39:
  Bumping version to 1.35.39
  Update to latest models
  • Loading branch information
aws-sdk-python-automation committed Oct 11, 2024
2 parents 003ebdb + 4c97570 commit 5efce9e
Show file tree
Hide file tree
Showing 11 changed files with 224 additions and 126 deletions.
27 changes: 27 additions & 0 deletions .changes/1.35.39.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
[
{
"category": "``appflow``",
"description": "Doc only updates for clarification around OAuth2GrantType for Salesforce.",
"type": "api-change"
},
{
"category": "``elbv2``",
"description": "Add zonal_shift.config.enabled attribute. Add new AdministrativeOverride construct in the describe-target-health API response to include information about the override status applied to a target.",
"type": "api-change"
},
{
"category": "``emr``",
"description": "This release provides new parameter \"Context\" in instance fleet clusters.",
"type": "api-change"
},
{
"category": "``guardduty``",
"description": "Added a new field for network connection details.",
"type": "api-change"
},
{
"category": "``robomaker``",
"description": "Documentation update: added support notices to each API action.",
"type": "api-change"
}
]
10 changes: 10 additions & 0 deletions CHANGELOG.rst
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,16 @@
CHANGELOG
=========

1.35.39
=======

* api-change:``appflow``: Doc only updates for clarification around OAuth2GrantType for Salesforce.
* api-change:``elbv2``: Add zonal_shift.config.enabled attribute. Add new AdministrativeOverride construct in the describe-target-health API response to include information about the override status applied to a target.
* api-change:``emr``: This release provides new parameter "Context" in instance fleet clusters.
* api-change:``guardduty``: Added a new field for network connection details.
* api-change:``robomaker``: Documentation update: added support notices to each API action.


1.35.38
=======

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.35.38'
__version__ = '1.35.39'


class NullHandler(logging.Handler):
Expand Down
40 changes: 20 additions & 20 deletions botocore/data/appflow/2020-08-23/endpoint-rule-set-1.json
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,6 @@
]
}
],
"type": "tree",
"rules": [
{
"conditions": [
Expand Down Expand Up @@ -83,7 +82,8 @@
},
"type": "endpoint"
}
]
],
"type": "tree"
},
{
"conditions": [
Expand All @@ -96,7 +96,6 @@
]
}
],
"type": "tree",
"rules": [
{
"conditions": [
Expand All @@ -110,7 +109,6 @@
"assign": "PartitionResult"
}
],
"type": "tree",
"rules": [
{
"conditions": [
Expand All @@ -133,7 +131,6 @@
]
}
],
"type": "tree",
"rules": [
{
"conditions": [
Expand Down Expand Up @@ -168,7 +165,6 @@
]
}
],
"type": "tree",
"rules": [
{
"conditions": [],
Expand All @@ -179,14 +175,16 @@
},
"type": "endpoint"
}
]
],
"type": "tree"
},
{
"conditions": [],
"error": "FIPS and DualStack are enabled, but this partition does not support one or both",
"type": "error"
}
]
],
"type": "tree"
},
{
"conditions": [
Expand All @@ -200,14 +198,12 @@
]
}
],
"type": "tree",
"rules": [
{
"conditions": [
{
"fn": "booleanEquals",
"argv": [
true,
{
"fn": "getAttr",
"argv": [
Expand All @@ -216,11 +212,11 @@
},
"supportsFIPS"
]
}
},
true
]
}
],
"type": "tree",
"rules": [
{
"conditions": [],
Expand All @@ -231,14 +227,16 @@
},
"type": "endpoint"
}
]
],
"type": "tree"
},
{
"conditions": [],
"error": "FIPS is enabled but this partition does not support FIPS",
"type": "error"
}
]
],
"type": "tree"
},
{
"conditions": [
Expand All @@ -252,7 +250,6 @@
]
}
],
"type": "tree",
"rules": [
{
"conditions": [
Expand All @@ -272,7 +269,6 @@
]
}
],
"type": "tree",
"rules": [
{
"conditions": [],
Expand All @@ -283,14 +279,16 @@
},
"type": "endpoint"
}
]
],
"type": "tree"
},
{
"conditions": [],
"error": "DualStack is enabled but this partition does not support DualStack",
"type": "error"
}
]
],
"type": "tree"
},
{
"conditions": [],
Expand All @@ -301,9 +299,11 @@
},
"type": "endpoint"
}
]
],
"type": "tree"
}
]
],
"type": "tree"
},
{
"conditions": [],
Expand Down
8 changes: 5 additions & 3 deletions botocore/data/appflow/2020-08-23/service-2.json
Original file line number Diff line number Diff line change
Expand Up @@ -5,11 +5,13 @@
"endpointPrefix":"appflow",
"jsonVersion":"1.1",
"protocol":"rest-json",
"protocols":["rest-json"],
"serviceFullName":"Amazon Appflow",
"serviceId":"Appflow",
"signatureVersion":"v4",
"signingName":"appflow",
"uid":"appflow-2020-08-23"
"uid":"appflow-2020-08-23",
"auth":["aws.auth#sigv4"]
},
"operations":{
"CancelFlowExecutions":{
Expand Down Expand Up @@ -4444,7 +4446,7 @@
},
"oAuth2GrantType":{
"shape":"OAuth2GrantType",
"documentation":"<p>Specifies the OAuth 2.0 grant type that Amazon AppFlow uses when it requests an access token from Salesforce. Amazon AppFlow requires an access token each time it attempts to access your Salesforce records.</p> <p>You can specify one of the following values:</p> <dl> <dt>AUTHORIZATION_CODE</dt> <dd> <p>Amazon AppFlow passes an authorization code when it requests the access token from Salesforce. Amazon AppFlow receives the authorization code from Salesforce after you log in to your Salesforce account and authorize Amazon AppFlow to access your records.</p> </dd> <dt>CLIENT_CREDENTIALS</dt> <dd> <p>Amazon AppFlow passes client credentials (a client ID and client secret) when it requests the access token from Salesforce. You provide these credentials to Amazon AppFlow when you define the connection to your Salesforce account.</p> </dd> <dt>JWT_BEARER</dt> <dd> <p>Amazon AppFlow passes a JSON web token (JWT) when it requests the access token from Salesforce. You provide the JWT to Amazon AppFlow when you define the connection to your Salesforce account. When you use this grant type, you don't need to log in to your Salesforce account to authorize Amazon AppFlow to access your records.</p> </dd> </dl>"
"documentation":"<p>Specifies the OAuth 2.0 grant type that Amazon AppFlow uses when it requests an access token from Salesforce. Amazon AppFlow requires an access token each time it attempts to access your Salesforce records.</p> <p>You can specify one of the following values:</p> <dl> <dt>AUTHORIZATION_CODE</dt> <dd> <p>Amazon AppFlow passes an authorization code when it requests the access token from Salesforce. Amazon AppFlow receives the authorization code from Salesforce after you log in to your Salesforce account and authorize Amazon AppFlow to access your records.</p> </dd> <dt>JWT_BEARER</dt> <dd> <p>Amazon AppFlow passes a JSON web token (JWT) when it requests the access token from Salesforce. You provide the JWT to Amazon AppFlow when you define the connection to your Salesforce account. When you use this grant type, you don't need to log in to your Salesforce account to authorize Amazon AppFlow to access your records.</p> </dd> </dl> <note> <p>The CLIENT_CREDENTIALS value is not supported for Salesforce.</p> </note>"
},
"jwtToken":{
"shape":"JwtToken",
Expand Down Expand Up @@ -4523,7 +4525,7 @@
},
"oauth2GrantTypesSupported":{
"shape":"OAuth2GrantTypeSupportedList",
"documentation":"<p>The OAuth 2.0 grant types that Amazon AppFlow can use when it requests an access token from Salesforce. Amazon AppFlow requires an access token each time it attempts to access your Salesforce records.</p> <dl> <dt>AUTHORIZATION_CODE</dt> <dd> <p>Amazon AppFlow passes an authorization code when it requests the access token from Salesforce. Amazon AppFlow receives the authorization code from Salesforce after you log in to your Salesforce account and authorize Amazon AppFlow to access your records.</p> </dd> <dt>CLIENT_CREDENTIALS</dt> <dd> <p>Amazon AppFlow passes client credentials (a client ID and client secret) when it requests the access token from Salesforce. You provide these credentials to Amazon AppFlow when you define the connection to your Salesforce account.</p> </dd> <dt>JWT_BEARER</dt> <dd> <p>Amazon AppFlow passes a JSON web token (JWT) when it requests the access token from Salesforce. You provide the JWT to Amazon AppFlow when you define the connection to your Salesforce account. When you use this grant type, you don't need to log in to your Salesforce account to authorize Amazon AppFlow to access your records.</p> </dd> </dl>"
"documentation":"<p>The OAuth 2.0 grant types that Amazon AppFlow can use when it requests an access token from Salesforce. Amazon AppFlow requires an access token each time it attempts to access your Salesforce records.</p> <dl> <dt>AUTHORIZATION_CODE</dt> <dd> <p>Amazon AppFlow passes an authorization code when it requests the access token from Salesforce. Amazon AppFlow receives the authorization code from Salesforce after you log in to your Salesforce account and authorize Amazon AppFlow to access your records.</p> </dd> <dt>JWT_BEARER</dt> <dd> <p>Amazon AppFlow passes a JSON web token (JWT) when it requests the access token from Salesforce. You provide the JWT to Amazon AppFlow when you define the connection to your Salesforce account. When you use this grant type, you don't need to log in to your Salesforce account to authorize Amazon AppFlow to access your records.</p> </dd> </dl> <note> <p>The CLIENT_CREDENTIALS value is not supported for Salesforce.</p> </note>"
}
},
"documentation":"<p> The connector metadata specific to Salesforce. </p>"
Expand Down
Loading

0 comments on commit 5efce9e

Please sign in to comment.