ACE configuration "keystore" integration server configuration object type is not GitOps friendly

We are running ACE SC-2 release pods on CP4I on Openshift on Azure, we have complex CI/CD pipelines + ArgoCD to rollout ACE integrations. Sometimes we need ACE pods with unique keystores as some partners require mTLS and usually issue a personal certificate (.p12). We upload this certificate to Azure key vault from where it is automatically synced as an Openshift secret of type "kubernetes.io/tls" (with a tls.crt and tls.key Data fields) using a utility.

The issue is that the ACE configuration "keystore" integration server configuration object type expects a generic Openshift secret which contains the .p12 keystore itself (see command below), this is not GitOps friendly as we need a script or pipeline to extract the synced secret and create a generic secret which is against our configuration driven policy in our company.

It would be great if IBM can fix this by accepting Openshift secret of type "kubernetes.io/tls" and then building a .p12 file underneath and mounting it to the ACE pod.

Official documentation: https://www.ibm.com/docs/en/app-connect/containers_cd?topic=types-keystore-type

oc -n ace create secret generic conf-keystore --from-file=configuration=ace.p12

apiVersion: appconnect.ibm.com/v1beta1
kind: Configuration
metadata:
  name: conf-keystore
  namespace: ace
spec:
  secretName: conf-keystore
  type: keystore
  version: 12.0.12.0-r1-lts