Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request (PR) description
Remove openvpn::deploy from this module.
The
openvpn::deploy
classes + facts introduced in (#261). The facts has a lot of outstanding issue in the history of this module.The fact based approach has multiple issues:
The first 2 issues should be a clear statement that returning to the fact based approch is not a option. Each default setup on puppet 7.10 and higher will emit a warning, if this module is in use.
A proposal to replace facts by deferred functions (#410) also never works
I'm strongly recommend, if this functionality is needed to use a dedicated modules for this.
Example (but outdated):
Major issue that I see: Even I'm not using the
openvpn::deploy
classes, the facts containing the private keys and published to puppetdb are NOT toggleable. If Foreman is used in the setup, all the private keys are exposed to the user base of Foreman.By separate the logic into a dedicated puppet module, no sensitive facts are generated by default.
In general, use a Hashicorp Vault to exchange private keys in your setup, instead abuse puppet for it.
This Pull Request (PR) fixes the following issues
Fixes #352
Fixes #421