fog-core
fog-core copied to clipboard
fog
fog's core, shared behaviors without API and provider specifics
Hi. I found out that Fog::Collection donsn't do `lazy_load` while being converted by `Kernel.Array` method that implicitly called by several Array methods. For example, `Array#concat` converts its operand by `Array()`...
(This is spun out of a discussion started [here](https://github.com/cloudfoundry/cloud_controller_ng/issues/2647)) Some provider gems are not being very actively maintained, and there does not a coordinated effort to ensure inter-compatibility between the...
For example, we create a model with those attributes: ``` (#)> attributes => {:name=>"fog-test-networkscol-9ca8d6cc-4686-4d3f-9cd2-8d28a9383154", :ipv4_range=>"10.240.133.0/24"} ``` When created actually turns into proper model fields: ```(#)> attributes => {:name=>"fog-test-networkscol-9ca8d6cc-4686-4d3f-9cd2-8d28a9383154", :ipv4_range=>"10.240.133.0/24"} my_network...
See fog/fog#1973 for more info.
This is work in progress specification for adding core functionality to register a provider and its services within `Fog::Core` making the register available to third party applications. This is an...
This issue was spurred by https://github.com/fog/fog/pull/2939. This is certainly not the first time, I have seen downstream developers expect to use string and symbols interchangeably. Doing a quick search through...
# Problem Unable to require fog/rackspace which was working fine in the previous versions and got busted in v2.3.0. In #269, the author introduced the `const_defined?` method to check whether...
@geemus Related to https://github.com/fog/fog-aws/pull/711
