Use a custom config path target when running unattended-setup

[krishardy]

The issue:

When setting up warpgate to run as a non-root user, warpgate unattended-setup fails with insufficient permissions because it needs to create /etc/warpgate.yaml and the data path. To work around this, you must currently run it as root and then change permissions of the data path and ensure that /etc/warpgate.yaml can be read by the user that warpgate will run as.

The expected behaviour:

warpgate unattended-setup should support a custom config path (such as warpgate unattended-setup --config <custom_path> ...). This will save the configuration yaml file to the provided custom path.

I am intending to implement this change, and an opening this issue in order to start any necessary communications.

[Christian-Little-Tava]

You can use warpgate --config unattended-setup

And that seems to make it happy