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

Do not require openvpn::client for client specific configs #279

Closed
wants to merge 1 commit into from

Conversation

spacedog
Copy link

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 #229

Signed-off-by: Anton Baranov abaranov@linuxfoundation.org

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>
@bastelfreak
Copy link
Member

@spacedog thanks for the PR. Can you please rebase?

@juniorsysadmin juniorsysadmin added the bug Something isn't working label Aug 20, 2018
@bastelfreak
Copy link
Member

Hi. I'm going to close this PR due to inactivity. Please reopen and rebase it if you're still interested.

@bastelfreak bastelfreak closed this Jul 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Client specific configs with extca enabled
3 participants