Daniel McCarney

> have the creation of streisand-host create generated-docs/gateway-password.txt. I suspect this is a regression. It used to be the case that running `vagrant up` would ensure the `streisand-host` was using...

> have the creation of streisand-host create generated-docs/gateway-password.txt. I fixed this as part of https://github.com/StreisandEffect/streisand/pull/1047

We already run [Streisand in an LXC](https://github.com/jlund/streisand/blob/master/tests/development-setup.yml#L138:L152) for CI :-) Basically everything works as-expected. StrongSwan requires [building & installing the kernel modules on the host](https://github.com/jlund/streisand/blob/master/tests/development-setup.yml#L69:L99). WireGuard would require the same...

I think I would prefer to see better support for migrating the full state between two servers instead of just the gateway password.

There seems to be some interest in providing "clean" DNS from a Streisand instance without having to use one of the VPN providers/tunnel all traffic through. I'm in favour of...

I'm particularly adverse to adding new provider support to Streisand. It's a lot of work, the libraries/APIs for providers change/break frequently, and it adds a huge test burden. Azure support...

> @cpu is there not an equiv of saltstack's SaltCloud drivers that obfuscate away the integration with popular providers in Ansible? I'm not sure. I only have the way we...

@damko That sounds interesting but complex & a fair deviation from the services/deployment model of the existing project. I would encourage you to experiment with a fork of Streisand &...

This would be a pretty major departure from the current state of affairs. It sounds interesting, but a lot of work and probably something that would be easier to accomplish...

In general I feel like this is a pretty niche use-case (if others are interested they should speak up). It will increase the attack surface of a Streisand instance and...