multi-cluster and shared appgw setup using Helm

[arctech7]

My goal is to use two clusters and share them using a single appgw.
I've enabled sharing in my helm config.
Using my ingress yaml deploys the ingress with backend pools/settings/rules/listeners etc for 1st AKS but when I deploy the same for 2nd AKS it will clear everything and create a new backend pools/settings/rules/listeners of the 2nd yaml

I tried using AzureIngressProhibitedTarget to not touch what was created in 1st AKS by setting the hostname as dev-api.example.com
In the 2nd cluster I also added this for hostname as test-api.example.com. I've also tried switching this around between the two clusters.

DEV yaml:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress-api
namespace: default
annotations:
kubernetes.io/ingress.class: azure/application-gateway
appgw.ingress.kubernetes.io/backend-path-prefix: "/"
appgw.ingress.kubernetes.io/appgw-ssl-certificate: "wildcard-certificate"
appgw.ingress.kubernetes.io/ssl-redirect: "true"

spec:
rules:

• host: dev-api.example.com
• http:
  paths:
  • path: /manager/*
    pathType: Prefix
    backend:
    service:
    name: manager-api
    port:
    number: 80

QA yaml:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress-api
namespace: default
annotations:
kubernetes.io/ingress.class: azure/application-gateway
appgw.ingress.kubernetes.io/backend-path-prefix: "/"
appgw.ingress.kubernetes.io/appgw-ssl-certificate: "wildcard-certificate"
appgw.ingress.kubernetes.io/ssl-redirect: "true"

spec:
rules:

• host: test-api.example.com
• http:
  paths:
  • path: /manager/*
    pathType: Prefix
    backend:
    service:
    name: manager-api
    port:
    number: 80

helm version version.BuildInfo{Version:"v3.10.0", GitCommit:"ce66412a723e4d89555dc67217607c6579ffcb21", GitTreeState:"clean", GoVersion:"go1.18.6"}

Using Helm chart ingress-azure-1.5.2. I've also tried 1.6.0-rc1

Is what I am trying to do the correct way or not?
Should it not create two seperate backend pools/settings/rules/listeners etc?
My helm-config.yaml also has the subResourceNamePrefix set for each cluster corresponding to dev and qa to distinguish between the two.