crossplane-contrib / provider-aws

Crossplane AWS Provider
Apache License 2.0
429 stars 367 forks source link

RDS aurora-postgresql Serverless Required Fields Bug #2070

Open gl-af opened 3 months ago

gl-af commented 3 months ago

Hey! I'm trying to create an RDS aurora-postgresql instance and am running into what I think is a bug. Here's a snippet of my composition:

- name: instantiate-db
  base:
    apiVersion: rds.aws.upbound.io/v1beta1
    kind: Instance
    spec:
      forProvider:
        #allocatedStorage: 20
        dbName: backstage
        engine: aurora-postgresql
        instanceClass: db.serverless
        storageEncrypted: true
        username: root
        manageMasterUserPassword: false
        passwordSecretRef:
           key: password
           name: backstage-postgres-secret
           namespace: orchestration
        autoGeneratePassword: true
        monitoringInterval: 60
        applyImmediately: true
        skipFinalSnapshot: true
        region: eu-west-1
        dbSubnetGroupNameSelector:
          matchControllerRef: true
        vpcSecurityGroupIDSelector:
          matchControllerRef: true
      writeConnectionSecretToRef:
        name: example-dbinstance-out
        namespace: orchestration

When I create a claim for this composition my instance fails to create with the following error: {0 \"allocated_storage\": required field is not set []} My understanding is this field should not be necessary given I'm using instanceClass: db.serverless, so this seems like a bug to me.

In any case, if I do uncomment this field above, I then get this error: InvalidParameterCombination: Invalid storage size for engine name aurora-postgresql and storage type aurora: 20

Can anyone confirm this is a bug?

Thanks.

github-actions[bot] commented 1 week ago

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. 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.