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

12 commits

Author SHA1 Message Date
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
Diego Desani
49150c30d2 - Updated "@host" variable to "noc.newservers.com" which is the current host for API calls
- Added two calls: add_server_by_configuration.rb and list_configurations.rb
-- These calls should be used instead of add_server and list_plans, although we still support them.
- General comments were updated.
2012-08-24 00:17:43 -04:00
James Herdman
97b16d08d2 Remove absolute path when requiring 2012-05-26 11:27:28 -04:00
John Wang
3a17e5174b Switch from NewServers to BareMetalCloud for #773
Includes changing from new_servers to bare_metal_cloud as well as newservers to baremetalcloud.
2012-03-01 18:54:49 -08:00