Allow custom client options.

[ypid]

In case you want to add or change certain client options you can use the third parameter to specify them. This can for example be used in a multi-server setup to write all remotes in the client’s configuration and have clients choose which server to connect to. The following command can be used to achieve this:

docker run --rm -it --volumes-from $OVPN_DATA --volume /tmp/openvpn_clients:/etc/openvpn/clients kylemanna/openvpn ovpn_getclient $cn combined-save "remote vpn.example.com;remote vpn.example.net;remote-random"

Note that by specifying one or more remote parameter manually, the default remote entry is omitted. This was done to allow you to choose a order for the remotes because OpenVPN will try the remotes in the specified order unless the "remote-random" option set.

[kylemanna]

This doesn't scale well (scaling with more and more long tail tweaks) and complicates the scripts when the for the vast majority of users don't use these features. Perhaps there needs to be a path for more advanced config that uses another script?

[ypid]

Duplicating the ovpn_getclient would also make maintenance more difficult. Not sure if this is the way to go. I tired to keep this feature as generic as possible so that users can do with this what they need to configure. The normal user does not need to care about this. Just omit the parameter and use it as before.

[ypid]

Maybe leave the PR open so that others can still find it if needed? I think it has it’s use cases …