-
Notifications
You must be signed in to change notification settings - Fork 129
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
feature: add support to read certificate private keys from file-system #91
Comments
Awaiting real user need. If there are enough users who need this,I'll develop and push this out. |
Well in Gitlab CI, that could be useful. But there's more secrets than just certificates, some plugins contain sensitive tokens as configuration. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Blocked on the decision regarding security implications: #394 (review) |
Certificates are sensitive and can't be stored in plain-text.
In most use-cases, decK runs in a CI pipeline. In such a system, certificate private key and certificate can be provided to decK during runtime by CI via a file.
This avoids storing the certificate's private key in plaint-text in decK's state file.
The text was updated successfully, but these errors were encountered: