-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Tns small #681
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Tns small #681
Conversation
This file contains hidden or 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
Includes Hebrew language support, and you can set the desired partition count option to preconfigure the number of index partitions for a domain that uses the m2.2xlarge search instance type.
This was regressed here: aws@93b6ddb
Fix comment on WorkflowExecutionCollection#with_status and #count
…collection Modified document of `option[:instance_tenancy]`
Add DBSecurityGroupName to AuthorizeDBSecurityGroupIngress
Clarify log_level configuration docs
…r-chain use default credential provider in samples
According to http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPUT.html to enable redirect on an S3 object it needs to have 'x-amz-website-redirect' metadata key with new location value. When creating an object like so: ```ruby bucket.object['foo'].write('', metadata: { "x-amz-website-redirect" => "http://example.com" }, acl: :public_read ) ``` `x-amz-website-redirect` gets prepended with `x-amz-meta-` prefix thus breaking the redirect feature. This also affects any other meta data key which starts with 'x-amz'.
Includes message attributes support.
This update for Amazon Redshift introduces the ability to rename clusters.
Amazon S3 now supports server-side encryption using customer-provided encryption keys.
Added integration tests for copy snapshot and copy encrypted snapshot. Fixes aws#561
There are two notable behavior changes: 1. We do not yield to a block when there is zero content. This was causing an exception upstream in the code (in the case of client-side encryption, a cipher#update exception for no content). 2. We moved the truncated body check to be outside the Net::HTTP block, so that we don't clobber exceptions that were raised before that check. These issues have existed in the code for some time, but negative effects were only recently realized when a change in OpenSSL behavior resulted in empty packets being sent over the wire - yielding these caused exceptions downstream, rather than waiting for the content to be sent. That issue should no longer occur. Resolves issue aws#557.
This caused a regression in Ruby 1.8.7 which does not support %L in `strftime`. Fixes aws#563
s/erxisting/existing/
Correct EC2Provider expiration timeout
Fix a typo in add_queue_message.rb
AWS::SQS::Queue - use OpenSSL for Digest needs
References: aws#663
Adding support for task priority in the SDK data abstractions
Getting latest changes from remote.
Re-establish Ruby 1.8.7 compatibility
trevorrowe
added a commit
that referenced
this pull request
Feb 5, 2015
Merged into aws-sdk-v1, 97e4f9a. Thanks! |
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.
No description provided.