nir0s

I guess we could convert this to the explicit tar.gz URL and use it. Cloning would be a waste.

This somewhat addresses this: https://github.com/cloudify-cosmo/wagon/tree/Allow-to-use-git%2Bhttps-as-schema You can try it out. I haven't tested or finalized the implementation and there must be some edge cases I haven't addressed, but it should...

#12 adds the flag

Um.. anything on this? I see that there's a PR on this at #428 ... but it's sorta old.

Cloudify requires 2.7 On Feb 7, 2017 19:49, "Michael Littlejohn" wrote: > I'm having a similar issue, but I've been working through it on my forks > (as of earlier...

Unfortunately, Cloudify 3.1 was not designed to work with Centos 7. This is not a "limitation"per se but rather a state. Cloudify 3.3 will be supplied with Centos/RHEL 6.5/7 support....

Just an update. Cloudify 3.2.1 was released with a Centos 7 agent.

Usually, this happens when the provider context has already been posted. Where exactly are you trying to bootstrap? Is it a clean machine?

Are you running on Openstack by any chance and using a volume as your storage? Maybe you already bootstrapped once and am now using that same volume that already contains...