Closed serj1408 closed 5 years ago
This might be due to a change in fog-core. I believe we need to change our code to use autoload, similar to https://github.com/fog/fog-digitalocean/commit/5a023b40ee971529e2d3d5b8fb27869f5fb01934.
@chris1984: We have seen this in Foreman as well, so we should take care of this. Better sooner than later ;-)
@chris1984 - Have you completed any work on this? Any issues with me making an attempt at it?
cc: @ares, @ezr-ondrej
@tarcinil have at it
@tarcinil I would do what @timogoebel suggested and move to the autoload structure of the project. Have you done anything yet? Or should I do it?
@ezr-ondrej I have not started the work but that was my plan. I was planning on starting my work tonight and having something reviewable by the weekend.
If you'll give me about an hour, I'll produce testable version of that (WIP PR), I am finishing the testing. So you can base on that. I will move the files and give it some spins to see if it is not marginally broken.
After bit of an investigation I beleive the prefered way is the oposite of what digitalocean did. And I believe the finite answer is: https://github.com/fog/fog-core/blob/master/spec/compute_spec.rb.
Hello, we plan to bump fog in Foreman core soon, how far are we from having this ready? Thanks.
I believe, that @timogoebel agrees with the change and the PR is close to merging, but it is quite a big change, so it is up to him, how confident he is with merging.
I just merged the PR, will release 3.0.0 in the next couple of minutes.
How to avoid these type of warnings? It used to work and I can't find any new format documentation. Or is it a bug?
Ruby version 2.1.3