Tom Setkowski

I am getting this error too. Even if this faulty logging line is commented out, it still fails ``` Bringing machine 'default' up with 'openstack' provider...==> default: Finding flavor for...

After some time I found out this openstack bug. This has nothing to do with vagrant-openstack-provider. Any client will experience these problems, related bugs - https://bugs.launchpad.net/nova/+bug/1418529 - https://bugs.launchpad.net/mos/+bug/1450192

I definitely agree on the importance of being able to see the big picture. This is biggest issue blocking me from moving any projects to taiga. I'd love to see...

No merge syntax is not supported due to limitations of the parser. As suggested in https://github.com/tomzo/gocd-yaml-config-plugin/issues/72 replacing parser should fix this.

@rkrisztian I agree with you that order of tasks, artifacts, tabs makes more sense. But as you said, I have never noticed this as an issue until you mentioned it...

@maufonfa are you still experiencing this issue? It would nice to see your yaml

> You need something like: (data or params) + template => pipeline Yes of course. My main point is that it can also be flexible like: - `(data or params)...

> I was thinking of having an HTTPS level endpoint for plugins to register, just like an agent would I like this approach. Then "plugin" can be really anything, just...

> I was thinking of a per-plugin key. But, I'd need to think more deeply about the security it offers (does it?) vs. convenience. That's was my first thought too....

@arvindsv based on what @ketan [says about loader jruby voodoo magic](https://gitter.im/gocd?at=57ac8c41ff82b9fc7e7573b7), that might be a reason to stop going in this direction. I mean it sounds that adding jruby to...