Prod Deploy #1
Open
Prod Deploy #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![imtapps-ci[bot]](https://avatars.githubusercontent.com/u/847632?s=60&v=4){kind=small}
imtapps-ci
bot
commented
Nov 3, 2022
imtapps-ci
bot
commented
…ount query would be erroneous
Url encode query string for pure query
HTTP 204 responses have no body, but can have any headers they like, including, counter-intuitively, ones specifying the content type. This makes sure Boto won't pass a 0 length body to the json parser in response to a 204 status from Glacier. Unit test added to catch any regression.
Handle sigv4 non-string header values properly
This commits adds support to iam module for all currently available APIs related to Account Password Policy, introducing three new public methods: * get_account_password_policy() * delete_account_password_policy() * update_account_password_policy() IAM Password Policy and API reference: http://docs.aws.amazon.com/IAM/latest/UserGuide/Using_ManagingPasswordPolicies.html Signed-off-by: Luca Bruno <[email protected]>
This commit adds one unit and one integration test for the IAM Account Password Policy methods. Signed-off-by: Luca Bruno <[email protected]>
Signed-off-by: Luca Bruno <[email protected]>
…d-policy iam: add support for Account Password Policy APIs
Fix CloudSearch2 to work with IAM-based search and upload requests
Throw host warning for cloudsearch domain
Fix this error: InvalidCertificateException: Host sqs.cn-north-1.amazonaws.com.cn returned an invalid certificate
This fixes detection of signature version 4 for the eu-central-1 region when creating connections using the old-style URL, which is listed on the [supported regions and endpoints](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region): ``` s3-eu-central-1.amazonaws.com ```
…eft. Consider a table containing 100k items, a batch get is executed for 10k items. Of those 10k items about 50% do not exist. If a single batch request of 100 items (the DynamoDB limit) does not contain a result then no further results will be processed.
…keys should be processed rather than returning on first empty batch result.
boto.ses.connection::get_identity_dkim_attributes would call _make_request() but would incorrectly parse the XML response from AWS. If an input list with length greater than 1 was provided, this method would only return a response for a single list element. Adding DkimAttributes to list_markers and updating unit tests.
In Python, join is a method on string, not on list.
Fix Key.change_storage_class so that it obeys dst_bucket. Fixes boto#2752.
Add support for private hosted zones. Fixes boto#2785.
Update documentation for launchconfig. Fixes boto#2802.
Just return the ‘SetStackPolicyResponse’ whether its ‘SetStackPolicyResult’ or 'ResponseMetadata’
Add support for SQS PurgeQueue operation. Fixes boto#2806.
Pass version_id in copy if key is versioned. Fixes boto#2803.
Added suppport for additional fields in EMR objects. Fixes boto#2807.
DynamoDB table batch_get fails to process all remaining results if single batch result is empty. Fixes boto#2809.
Fix SES get_identity_dkim_attributes when input length > 1. Fixes boto#2810.
Fix bug by using correct string joining syntax. Fixes boto#2817.
Added ELB Attributes to docs. Fixes boto#2821.
This matches the public documentation and other AWS SDKs, which all use signature version 4 for these services. Note that this is no longer a detect_potential_sigv4, we should be using signature version 4 at all times for ec2/elb. I've also updated an assertion method to not require that the ignore_params_values actually exist in the request. We made a similar change in the AWS CLI a while back. All we care about is that we're not validating those params. We don't actually care if they're in the serialized params are not.
This will catch regressions if the signature version is ever switched back to ec2.
* switchover-sigv4: Add integ tests for sigv4 switchover Switch elb/ec2 over to signature version 4
Currently, when versioning is turned on or suspended for an s3 bucket calling `key.generate_url` will include a `versionId=null` when the key in question returns 'null' from s3 as the version id. This will cause a 403 when trying to use it.
|
Awaiting testing approval |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.