The AWS security group tests have been very unstable with 2 failures on
Travis per build. The majority is the mocked version of
`describe_security_groups` not working.
We have decided to disable it until someone makes time to figure out the
bug since it is affecting every build.
See https://travis-ci.org/fog/fog/jobs/25614603#L1105
- Add missing "Disk" properties
- Remove unnecessary property aliases
- Use "Operation" instead of the "backoff_if_unfound" method when
inserting a "Disk" or "Snapshot"
- When destroying a "Disk" asyncronous return the "Operation" model instead
of the raw operation response
- Add "list_aggregatted_disks" request
- If zone is not set on "all" and "get" methods, use the list aggregated
disks request (1 API call) instead of fetching all zones
- Fix a bug when inserting a snapshot (description was not merged at the
body request)
- Fix tests
- Add missing "Server" properties
- Remove unnecessary property aliases
- When destroying a "Server" asyncronously return the "Operation" model instead of the raw operation response
- If zone is not set on "all" and "get" methods, use the list aggregated servers request (1 API call) instead of fetching all zones
- Add "list_aggregated_servers" request
- Fix "attach_disk" request
- Fix "detach_disk" request
- Add "get_server_serial_port_output" request
- Add "reset_server" request
- Add "set_server_disk_auto_delete" request
- Add "set_server_scheduling" request
- Add "add_server_access_config" request
- Add "delete_server_access_config" request
- Fix "set_tags" request
S3 does not require normalization of S3 object keys and uses strict byte
comparison of object keys, not equivalent unicode character comparisons,
to store and retrieve objects. This means that storing and retrieving objects
with fog would cause the objects to be inaccessible by other libraries,
languages, and systems that don't normalize object keys. Given that there is
no benefit to normalization, except perhaps reducing byte count of object
keys, it ought to be removed.