SecretBackendConnection spec issues

[mattupstate]

What happened?

EDIT: Just noticed that the namespaced resource spec expects an array object at the spec.postgresql field. It doesn't map to the Terraform resource interface, but maybe there's a reason for that given how the API has to be modeled with OpenAPI?

When trying to submit a SecretBackendConnection resource I get the following error:

Error from server (BadRequest): error when creating "secret-backend-connection.yaml": SecretBackendConnection in version "v1alpha1" cannot be handled as a SecretBackendConnection: strict decoding error: unknown field "spec.forProvider.postgresql.connectionUrl", unknown field "spec.forProvider.postgresql.passwordSecretRef", unknown field "spec.forProvider.postgresql.username"

Example resource manifest:

apiVersion: database.vault.m.upbound.io/v1alpha1
kind: SecretBackendConnection
metadata:
  name: acme-example-postgres
spec:
  forProvider:
    name: acme-example-postgres
    backend: acme-nonprod/databases
    allowedRoles:
      - dba
      - app
    pluginName: postgresql-database-plugin
    postgresql:
      connectionUrl: postgresql://{{username}}:{{password}}@acme-example-infra-postgres-rw.default.svc.cluster.local:5432/acme
      username: vault
      passwordSecretRef:
        name: acme-example-infra-postgres-vault-password
        key: password
    verifyConnection: true
  providerConfigRef:
    kind: ClusterProviderConfig
    name: vault-cluster-provider-config

Running kubectl explain secretbackendconnections.database.vault.m.upbound.io.spec.forProvider.postgresql shows what you'd expect.

How can we reproduce it?

Setup Crossplane with the Vault provider and try submitting this resource.

What environment did it happen in?

Crossplane 2.0.2
xpkg.upbound.io/upbound/provider-vault:v3