[Bug]: AlloyDB cluster/instance do not populate writeConnectionSecretToRef secret

[drewwells]

Is there an existing issue for this?

• I have searched the existing issues

Affected Resource(s)

No response

Resource MRs required to reproduce the bug

apiVersion: alloydb.gcp.upbound.io/v1beta2
kind: Cluster
metadata:
  annotations:
    meta.upbound.io/example-id: alloydb/v1beta1/instance
  labels:
    testing.upbound.io/example-name: alloydb-test
  name: alloydb-test
spec:
  providerConfigRef:
    name: dwells
  writeConnectionSecretToRef:
    name: alloydb-creds-cluster
    namespace: dwells
  forProvider:
    location: us-central1
---
apiVersion: alloydb.gcp.upbound.io/v1beta2
kind: Instance
metadata:
  annotations:
    meta.upbound.io/example-id: alloydb/v1beta2/instance
  labels:
    testing.upbound.io/example-name: alloydb-test
  name: alloydb-test
spec:
  providerConfigRef:
    name: dwells
  writeConnectionSecretToRef:
    name: alloydb-creds-instance
    namespace: dwells
  forProvider:
    clusterSelector:
      matchLabels:
        testing.upbound.io/example-name: alloydb-test
    instanceType: PRIMARY
    machineConfig:
      cpuCount: 2

Steps to Reproduce

kubectl apply -f {yaml from above}

Notice that cluster and instance are created in GCP
A user is created in postgres alloydbsuperuser
List the secrets and they are empty

❯ k -n dwells get secret                                                
NAME                                                        TYPE                                DATA   AGE
alloydb-creds-cluster                                       connection.crossplane.io/v1alpha1   0      6m7s
alloydb-creds-instance                                      connection.crossplane.io/v1alpha1   0      6m7s

What happened?

I expect that the secrets are created with hostname, user, and password as mentioned in the documentation.

Relevant Error Output Snippet

No response

Crossplane Version

1.16.0

Provider Version

1.6.0

Kubernetes Version

v1.25.4

Kubernetes Distribution

GKE

Additional Info

No response

[github-actions]

This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.