Damien
Damien
I may have totally missed it, but it would be super nice to have some information on how those files should be parsed. The idea is that one could reuse...
Following on #27, we should have a set sub-command: ``` $ footloose config set cluster.machines[0].privileged true ```
I'd like to be able to setup the DNS servers instead of using the local /etc/resolved.conf when it points to a local dns cache.
We have two different code paths populating data for the JSON and table view for `footloose show`. We should only have a single one: - Machine.Status() returns a MachineStatus object...
There are a few things that could do with validation, empty fields should default to reasonable values, machine names having to have a `%d` in them, validate machine names are...
The `ignite` backend has been introduced and we have now two backends living in the same space with some `if backend == "ignite"` to distinguish code paths. It'd be nice...
I tuned a bit kind's `docker.Inpect` in https://github.com/kubernetes-sigs/kind/commit/7e8624bf1b318b03ac00d65b9c3359f7737aa946, we should update to this version.
Lucas noted apimachinery provides some benefits over plain old go objects. We may want to port our objects to it.
When stopping `footloose serve` we currently forget about all the objects that have been created (except the keys because they map to files on the filesystem). At the start of...
The whole footloose API is done with the machine name being the hostname of the machine, not the name of the container. `footloose show` should only display one name for...