Client specific configs with extca enabled #229
Comments
spacedog
added a commit
to spacedog/puppet-openvpn
that referenced
this issue
Mar 16, 2017
There is no need to require openvpn::client tpe as client configs don't rely on any of that type resources. It also not possible to use client_specific_config if extca_enabled is set to true for a server due to openvpn::client failure. Fixes voxpupuli#229 Signed-off-by: Anton Baranov <[email protected]>
|
@spacedog can you open a PR for that commit. I need this fix 😄 |
spacedog
added a commit
to spacedog/puppet-openvpn
that referenced
this issue
May 16, 2018
There is no need to require openvpn::client type as client configs don't rely on any of that type resources. It also not possible to use client_specific_config if extca_enabled is set to true for a server due to openvpn::client failure. Fixes voxpupuli#229 Signed-off-by: Anton Baranov <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
clinet_specific_configtype requiresopenvpn::clientwhich fails when server hasextca_enabled => true. It would be great if we can remove/workaround that dependency and useclinet_specific_configtype with extca enabled.The text was updated successfully, but these errors were encountered: