Éric Veiras

For me, it's not a distribution problem, it's just a clarity one: to keep "real"/production/runtime code separated from testing one. And maybe also a question of coherence, because in most...

@ek9 I agree with that, I want to have tests in the same repository as code, but I want to separate them in different directories.

I tried to use this undocumented option, removing all previous use of pillars/state_top/pillars-from-files. My kitchen.yml looks like ``` driver: name: vagrant provision: false provisioner: name: salt_solo formula: haproxy salt_install: bootstrap...

I'm not sure that `pillars-from-files` can be used to generate the top.sls, but you can use it to generate a pillar sls file and then include it in your pillar...

You get the point :)

If you already use ext_pillar, you can simply 'push' the same salt/salt-solo configuration to your Kitchen instances. You can overpass kitchen-salt limited directives pushing a salt-master-like configuration file. We use...

I tried to use the username/password but it didn't work, maybe because I also use the HTTP Auth. Error log from Nginx (anonymized): ``` - [24/Nov/2020:23:02:02 +0100] "GET /?do=login HTTP/1.1"...

I got the exact same problem trying to add a Debian 10 boot option using the released version 9.2.0-1

Hi, Is this issue still relevant? I just tried to start two Vagrant VM with some basic configuration (DHCP) and this hostmanager config ``` config.hostmanager.enabled = true config.hostmanager.manage_host = false...

It's weird because I don't have the hack. ``` $ vagrant -v Vagrant 1.9.1 $ vagrant plugin list vagrant-cachier (1.2.1) vagrant-env (0.0.3) vagrant-hostmanager (1.8.5) vagrant-libvirt (0.0.37) vagrant-mutate (1.2.0) vagrant-scp (0.5.7)...