Not sure if this can solve my problem (e.g: running certmagic as an extra process to do auto-renew existing certs) , or would one need to patch the certmagic to do this ?
I recommend just letting Caddy issue a new cert/key automatically (i.e. don’t give Caddy your old one). Issuing a cert is cheap and fast, so you don’t need to worry about it.
Why do you think you need this?
This means you can give it your own cert/keys to use for serving TLS connections, but not for managing issuance/renewal of those.
thank you
the main reason for using existing keypair is that i would need some extra fields/extension in the certificate. in some othe use cases, The private-key is provided.
I’m not sure I understand. What fields/extensions?
If you want to help push that feature request forwards, please post an explanation of why it would be useful for you (with technical detail please) to the issue.