[DynamoDB] Adopting table with PAY_PER_REQUEST validation error

[Juricakov]

Describe the bug
Adopting PAY_PER_REQUEST table results in validation error.

api error ValidationException: 2 validation errors detected: Value ''0''
      at ''globalSecondaryIndexUpdates.1.member.update.provisionedThroughput.writeCapacityUnits''
      failed to satisfy constraint: Member must have value greater than or equal to
      1; Value ''0'' at ''globalSecondaryIndexUpdates.1.member.update.provisionedThroughput.readCapacityUnits''
      failed to satisfy constraint: Member must have value greater than or equal to
      1

After manually clearing spec.provisionedTroughput and globalSecondaryIndexes.[].provisionedTroughput, we get

api error ValidationException: One or more parameter values were invalid: The only Updates for index: <index name> when TableThroughputMode is PAY_PER_REQUEST can be to OnDemandThroughput, WarmThroughput'

Steps to reproduce

1. Try adopting table that is configured with pay per request and global secondary indexes by setting annotations

    services.k8s.aws/adoption-fields: |
      {
        "tableName": "<name>"
      }
    services.k8s.aws/adoption-policy: adopt

Expected outcome
Table should be adopted without validation errors

Environment

• Kubernetes version 1.31
• Using EKS (yes/no), if so version? Yes
• AWS service targeted (S3, RDS, etc.) - DynamoDB

Using ack DynamoDB controller v1.4.0.

[github-actions]

Hello @Juricakov 👋 Thank you for opening an issue in ACK! A maintainer will triage this issue soon.

We encourage community contributions, so if you're interested in tackling this yourself or suggesting a solution, please check out our Contribution and Code of Conduct guidelines.

You can find more information about ACK on our website.

[Juricakov]

Update: I tried to use AdoptedResource instead of annotations, but it ends up with the same problem.

[michaelhtm]

Hi @Juricakov
I was not able to replicate this issue. The error message suggests that the read/writeCapacity is misconfigured.
Would you be able to share the output of kubectl get table <name> -oyaml? Redact any sensitive information.
Thanks!

[Juricakov]

Hey, we ended up identifying the issue, and it is not with the ACK operators, it's with a helm operator that we're using to create the DynamoDB Table CRDs.

Status after adoption is synced, it breaks on the next reconcile, which basically happens immediately after, so from my POV it looked like it was after adoption.

After adoption the array fields, ie indices are ordered alphanumerically, which may be different order than what the operator defines.

globalSecondaryIndices:
  - A
  - B
  - C

operator wants

globalSecondaryIndices:
  - C
  - A

and we get

globalSecondaryIndices:
  - C 
  - A
  - C # "leftover" from adoption

Sorry for the false report, thank you!