Signature method requires x-amz-security-token header.
[aws] Update aws error handling
Add RDS API version parameter option.
[openstack|image] Fix image reload
Update OpenStack Mocks
[AWS|EC2] Increased IOPS limit to 4000.
If there are no entries for the server then it returns null, but the code expects an array. Make it so.
If the attachment does not exist it raises a NoMethodError instead of NotFound.
The default value for metadata is nil, and this was raising NoMethodError on each_pair.
Match against the error object in both the old (against error.message) and the new (against error.response.body); return a hash from this method. In the rescue block, try hard to raise an exception that includes the code and message extracted from the error.
Instead of returning the cached image in collection, get (or find_by_id) method should refresh the image data. This will fix the reload method, as actually it doesn't really reload the image details.
RDS API has moved to 2013-05-15 and added additional methods and parameters to existing ones (such as NewDBInstanceIdentifier in ModifyDBInstance). It makes sense to use the new API version, however it requires more testing and possibly implementing additional methods. This commit allows the version to be passed when instantiating a fog object, so that this can be done piece-meal, without blocking existing fog users. Refs: #1931
Add PubliclyAccessible option to RDS.
[cli] Changes `fog --version` short option to `-v`
Recent versions of excon have a middleware component, Excon::Middleware::Expects and fog requests mostly record an expectation of a 200 status code. Some calls to AWS return status other than 200 and in some cases the error handling obscures the underlying error. Current handling parsed error.message; this instance of error is constructed by excon and includes the response as an attribute. The message is always something like 'Expected(200) <=> Actual(404 Not Found)' and so the parsing never succeeds. Instead we now attempt to parse error.response.body which should allow extraction of the underlying AWS Code value, which in turn will produce an exception that points to the actual underlying cause.
Looking at a number of similar Ruby based tools, Bundler, Rubygems, Pry and IRB all use lowercase v for the short option for `--version` Ruby itself uses `-v` for verbose but without any further arguments prints the version and exits.
* http://docs.aws.amazon.com/ses/latest/APIReference/API_VerifyDomainIdentity.html * Added Fog::Parsers::AWS::SES::VerifyDomainIdentity.
[rackspace|storage] Submit etags for file models
[rackspace] fixing broken tests
[google|compute] Upgrade GCE to v1beta15 and fix a bunch of bugs
[xenserver|compute] Small fix for snapshot tests added in #1914
Added support for [xenserver] snapshot