Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client specific configs with extca enabled #229

Open
spacedog opened this issue Mar 16, 2017 · 1 comment
Open

Client specific configs with extca enabled #229

spacedog opened this issue Mar 16, 2017 · 1 comment

Comments

@spacedog
Copy link

clinet_specific_config type requires openvpn::client which fails when server has extca_enabled => true. It would be great if we can remove/workaround that dependency and use clinet_specific_config type with extca enabled.

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 <abaranov@linuxfoundation.org>
@sebastianrakel
Copy link
Member

@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 <abaranov@linuxfoundation.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants