I would like to be able to use this plugin in combination with the Kubernetes Credentials Provider plugin, which automatically syncs Kubernetes secrets into Jenkins as credentials. This would require changing this plugin to support taking credential IDs instead of file paths. (This avoids us having to mount every secret we need into the Jenkins pod.)
This would also be an opportunity to move away from the Java KeyStore format, which is not well-known outside of the Java ecosystem. Even keytool itself kindly warns:
The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore keystore.ks -destkeystore keystore.ks -deststoretype pkcs12".
What feature do you want to see added?
I would like to be able to use this plugin in combination with the Kubernetes Credentials Provider plugin, which automatically syncs Kubernetes secrets into Jenkins as credentials. This would require changing this plugin to support taking credential IDs instead of file paths. (This avoids us having to mount every secret we need into the Jenkins pod.)
This would also be an opportunity to move away from the Java KeyStore format, which is not well-known outside of the Java ecosystem. Even
keytool
itself kindly warns:Upstream changes
No response