You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be helpful, particularly for large deployments, if this module deleted client configurations when their openvpn::client and openvpn::client_specific_config are no longer present.
Else, we end up with many old files left behind that are not useful and clutter the client-configs directory.
I know this can probably done by setting ensure to absent (and then removing the declaration entirely), but the cleanup that appears to be performed for the download-configs directory should also apply to client-configs.
I can't think of a use case where you'd need 'client specific config' but not a matching configuration and certificate available for download and distribution by puppet.
The text was updated successfully, but these errors were encountered:
It would be helpful, particularly for large deployments, if this module deleted client configurations when their
openvpn::client
andopenvpn::client_specific_config
are no longer present.Else, we end up with many old files left behind that are not useful and clutter the
client-configs
directory.I know this can probably done by setting
ensure
toabsent
(and then removing the declaration entirely), but the cleanup that appears to be performed for thedownload-configs
directory should also apply toclient-configs
.I can't think of a use case where you'd need 'client specific config' but not a matching configuration and certificate available for download and distribution by puppet.
The text was updated successfully, but these errors were encountered: