feat: refreshable exports #202
Conversation
Add possibility to switch the underlying Execs to "refreshonly" mode and handle over subscriptions to resource(s) as parameter. This fixes also a bug when p12 file is not renewed after the input file changed. Backward compatibility fully given.
|
Missed unit tests, my bad, will update in the next days 🙏 |
Co-authored-by: Kenyon Ralph <[email protected]>
pavelkovtunov
force-pushed
the
feat_refreshable_exports
branch
from
d0388eb to
4feddcc
Compare
|
It's a big issue in a project I'm currently working on: if the certificate/key pair changes, the p12 and decrypted key files are not updated. In our case, the input files are also defined as a file resource and puppet is aware of any changes on these files. The contents of certificate and key files is pulled from a DB. If there is an update - the file resources take care of it, but the downstream logic in this OpenSSL Module won't do anything because of static "creates" parameter. Before creating this PR I've wrote some code for our private workaround - just added an Exec for deleting the p12 and key file in case the input files change. I suppose some other boys and girls out there did the same to fix the issue locally. But IMHO it's always a better way to implement a generic solution for everyone. Hope it matches the community expectations :) |
Pull Request (PR) description
Add possibility to switch the underlying Execs to "refreshonly" mode and hand over subscriptions to resource(s) as parameter. This fixes also a bug when p12 file is not renewed after the input file changed. Backward compatibility fully given.
This Pull Request (PR) fixes the following issues
Fixes #131