1
0
Fork 0
mirror of https://github.com/fog/fog.git synced 2022-11-09 13:51:43 -05:00
Commit graph

28 commits

Author SHA1 Message Date
Paul Thornthwaite
ec8b940b2c Standardise on collection methods
Done with `rubocop --auto-correct --only CollectionMethods`
2014-05-26 16:22:07 +01:00
Paul Thornthwaite
2e0b7e545a Standardise empty lines throughout codebase
Done with `rubocop --auto-correct --only EmptyLineBetweenDefs,EmptyLines,EmptyLinesAroundBody`
2014-05-26 14:20:02 +01:00
Paul Thornthwaite
0e1daf3ddd [GH-2711] Replace Fog::Connection with XML shim
Unlike last attempt this replaces Fog::Connection with
Fog::XML::Connection which should be directly compatible.

Fog::Connection is there for old PRs but should be removed real soon.

Providers using JSON should be able to replace "XML" with "Core" within
their code to cut down on the dependency.

If I get the time I may attempt to clean up some but testing with Mock
will mean that is mostly educated guesswork.
2014-02-27 00:54:17 +00:00
Paul Thornthwaite
5007aac401 Revert "[core] Replace Fog::Connection with stable version"
This reverts commit 7ee3535d99.
2014-02-26 09:52:02 +00:00
Paul Thornthwaite
7ee3535d99 [core] Replace Fog::Connection with stable version
Fog::Connection mixed in XML parsing via the `parser` argument which
wasn't much use for the majority of APIs using JSON.

This adds the deprecation warning and attempts to update providers to
the correct version of Connection that they need.

Either the cleaner `Fog::Core::Connection` or if reliant on the XML
parsing still `Fog::XML::SAXParserConnection`

The SAX parser will be moving to `fog/xml` fairly soon.
2014-02-25 21:42:34 +00:00
Paul Thornthwaite
15ef5365e5 Require json or xml in provider cores
Since `fog-json` was extracted from `fog` it means if you rely on:

    require "fog/provider/compute"

`Fog::JSON` was not defined although it was supposed to be a supported
use case.

This adds the requires for JSON or XML based APIs based on a quick scan
of each provider to declare the required part.

AWS seems to be relying on both. Which is nice.

Providers relying on native code dependencies
2014-02-19 14:58:00 +00:00
Paul Thornthwaite
8483a599f2 Remove trailing whitespace 2014-02-19 12:30:59 +00:00
Paul Thornthwaite
a72433d2f8 Remove duplicate requires from services
Following work on reorganising the requires, there was an inconsistent
approach to where service wrappers are required. (Fog::Compute...)

Since they should be standardised and shared across providers (although
they really aren't yet) they have been moved to `fog-core` gem.

Each provider has their own `lib/fog/{provider}/core` files that is
required by each of their services. These files should all require
`fog/core` which already required most or these.

So this removes the extra cases to concentrate them in core.
2014-02-13 17:44:48 +00:00
Lance Ivy
f9a5b9e942 don't require service when registering it
services will still be required when you:
* require them yourself
* require the entire provider (which requires all services)
2014-02-01 22:02:40 -05:00
Lance Ivy
1cdd969a34 create core for each provider. keep load hook for provider. 2014-02-01 21:13:17 -05:00
Lance Ivy
26c6766b09 normalize requires syntax 2014-02-01 12:50:48 -05:00
Brian D. Burns
40e8f458f2 use Fog::JSON 2013-11-19 00:51:57 -05:00
Erik Michaels-Ober
f2bd2404d1 Revert "Updated gem spec to require json rather than multi_json"
This reverts commits: 66638b25d7,
3f0314dbd1, and
18ce4b7eca.

Since google-api-client was added as a dependency in afa9b025e9,
multi_json is a de facto dependency of fog, so this is a needless layer.
If #1034 is still an issue, I'd be happy to ship a version of multi_json
that requires rubygems >= 1.3.5.
2013-05-06 04:05:36 -07:00
Kyle Rames
7b07d74e14 Merge pull request #1730 from rackspace/json_lib
[Core] Updated Fog::JSON to use JSON gem by default
2013-04-08 08:13:46 -07:00
Sergio Rubio
9fd4482c85 [dreamhost|dns] added missing changelog 2013-04-04 19:00:02 +02:00
Kyle Rames
66638b25d7 Updated gem spec to require json rather than multi_json; Fog::JSON will attempt to load and use multi_json first and then fallback to require json; removed hard coded references to multi_json 2013-04-03 08:42:45 -05:00
Sergio Rubio
3ba2f45cd9 [dreamhost|dns] drop uuid gem requirements, not needed
Not sure to understand unique_id documentation from Dreamhost, but
experimentation shows that a new UUID every request isn't required
and Dreamhost says it's optional.

http://wiki.dreamhost.com/Application_programming_interface#Required
2013-01-22 21:32:23 +01:00
Sergio Rubio
e469d70eaf [dreamhost|dns] Updated Dreamhost/DNS getting started guide 2013-01-22 21:08:50 +01:00
Sergio Rubio
6d2a500b76 [dreamhost|dns] Zone.records: list only records matching the current zone 2013-01-22 20:36:59 +01:00
Sergio Rubio
6dcbd01695 [dreamhost|dns] Moved getting started guide to examples/dns 2013-01-22 20:14:50 +01:00
Sergio Rubio
c38aa22e3a [dreamhost|dns] Do not add duplicated zones to the Zones collection 2013-01-22 20:13:09 +01:00
Sergio Rubio
19c8c4d877 [dreamhost|docs] Added getting started guide, initial release 2013-01-21 23:53:59 +01:00
Sergio Rubio
9dd24ab2bd [dreamhost|dns] Emulate zone model and collection, added tests
Dreamhost API has no concept of Zone, but we can emulate it.
2013-01-21 23:26:30 +01:00
Sergio Rubio
90b5d84c6d [dreamhost|dns] added Record model tests, fix Record.save
Record.save was missing attribute merging before returning
2013-01-21 22:16:56 +01:00
Sergio Rubio
87d81967fa [dreamhost|dns] Removed get_record request
- The request does not map to a Dreamhost API request, remove it.
- Updated the Records collection to use list_records instead of
  get_record in Records#get
- Added Records collection model test
2013-01-21 21:36:11 +01:00
Sergio Rubio
2650d6d53b [dreamhost|dns] remove silly debugging code 2013-01-21 19:43:49 +01:00
Sergio Rubio
705cf8e2d8 [dreamhost|dns] remove connection deprecation notices 2013-01-19 23:39:33 +01:00
Sergio Rubio
782b935a9b * [dreamhost|dns] initial import 2013-01-19 23:20:38 +01:00