Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Refactor with an eye toward separation of git-core and specific provider #20
Not sure about this.
That pattern got setup as a way to defer the
I may be missing something as to why it is being removed because it can be required multiple times if you must require it before the call to
Also not sure which other providers expose an identity service.
Best way I know to determine this is modify your fog dev env to use your local fog-core, run the test suite, and see what breaks. :D
On February 25, 2014 at 3:04:43 PM, Chris Johnson (firstname.lastname@example.org) wrote:
Will this change break other providers, other than the Rackspace provider? It just occurred to me that it might be useful to validate that...
I have the new openstack provider (named openstackcommon) working locally with that line commented out. With that line of code in place, it fails.
We are replacing the current provider, not updating it. In the new gem, the folder structure is not the same. As I understand it, the fog//identity is used to refer to the file that contains the identity service provider. In the single fog project, all of the providers were under the fog project, and this require worked. In this new approach, that is no longer the case.
Does this help?
The more I think about this though, the more convinced I am that this might break existing providers if it goes in. Let me test this with the existing HP provider before moving forward here; we might have to adjust...