Is your feature request related to a problem? Please describe.
Currently, some azure services require the certificate to be stored under certificates in the keyvault, they will not accept certificate in secrets. It also has to be in PKCS12 format.

Currently, the best way to generate certificates on kubernetes it to use cert-manager + let's encrypt. The issue is that cert-manager does not allow for creation of passwordless pkcs12 certs, and external-secrets does not support pkcs12 with passwords.

In theory, ESO gives us template and "pemToPkcs12", which can be used like so pemToPkcs12 (index . "tls.crt" ) ( index . "tls.key" ). The issue is that this won't actually work with azure keyvault certificates. It will error out with "Could not parse certificate value as PKCS#12, DER or PEM".

Furthermore, even if it were to be stored as a secret, it will only ever be uploaded as base64, not raw p12, even if b64dec is added at the end.

Describe the solution you'd like
Make it possible to upload the certificate to azure keyvault certificates, or at the very least give us ability to store the secret as a raw p12 instead of base64. Maybe with something like pemToRawPkcs12 template function.