Brett Hartley

We have dev zones with `-` in the name, dating back to v3 days (maybe even earlier), so we modify the schema to allow it (since the other options are...

I'm struggling to see how >You can have a copy of the configuration files that we ship in a slightly different location - and then point to your version. is...

For us, this happens with any database with `_` in the name, suggesting it's an issue with the handling of `_`s

``` docker-machine create --driver openstack --openstack-availability-zone nova --openstack-flavor-id 2002 --openstack-image-name xenial-gitlab-slave --openstack-net-name gitlab-autoscale --openstack-floatingip-pool nova --openstack-sec-groups ssh,default,icmp,autoscale --openstack-ssh-user "ubuntu" test1 > test1.txt | docker-machine create --driver openstack --openstack-availability-zone nova --openstack-flavor-id...

Just repinging on this issue, because it's still not actually fixed (even in master), so it shouldn't really be closed

Also, the closing message suggests the problem is that specific queries can't be created, but we use specific queries on this zone. Only an admin can create them, but since...

Worth noting the CAT_INVALID_USER was triggered by the fact that I didn't notice the jobs config, so as a side point, could the entries in metalnx.properties be documented please?