The real issue might be within Libcloud, but since we are using 1.5.0 from 2016 I'm not going to file issue there. This might be fixed just by upgrading libcloud. I only did the hacky fix for non-azure else branch as I have no way to test if azure has the same problem.
Fixes #43
The real issue might be within Libcloud, but since we are using 1.5.0 from 2016 I'm not going to file issue there. This might be fixed just by upgrading libcloud. I only did the hacky fix for non-azure else branch as I have no way to test if azure has the same problem.