What happened?
The DynamoDB Table managed resource appears to be missing support for enabling DynamoDB Time To Live (TTL) / TimeToLiveSpecification.
Terraform/OpenTofu exposes this as a ttl block, and Upbound provider-aws-dynamodb exposes ttl.attributeName and ttl.enabled.
Without this field, provider-aws cannot declaratively enable TTL on DynamoDB tables.
How can we reproduce it?
Try to configure TTL on a DynamoDB table via provider-aws DynamoDB Table. There is no field in the CRD/spec to set TTL.
Expected conceptual shape:
apiVersion: dynamodb.aws.crossplane.io/v1alpha1
kind: Table
spec:
forProvider:
region: us-east-1
ttl:
attributeName: expiresAt
enabled: true
What environment did it happen in?
Provider version: v0.56.0 / v0.58.0
Kubernetes version:
Crossplane version:
AWS region:
Related references
Terraform/OpenTofu aws_dynamodb_table supports ttl.
Upbound provider-aws-dynamodb Table exposes ttl.
What happened?
The DynamoDB Table managed resource appears to be missing support for enabling DynamoDB Time To Live (TTL) /
TimeToLiveSpecification.Terraform/OpenTofu exposes this as a
ttlblock, and Upbound provider-aws-dynamodb exposesttl.attributeNameandttl.enabled.Without this field, provider-aws cannot declaratively enable TTL on DynamoDB tables.
How can we reproduce it?
Try to configure TTL on a DynamoDB table via provider-aws DynamoDB Table. There is no field in the CRD/spec to set TTL.
Expected conceptual shape:
What environment did it happen in?
Provider version: v0.56.0 / v0.58.0
Kubernetes version:
Crossplane version:
AWS region:
Related references
Terraform/OpenTofu aws_dynamodb_table supports
ttl.Upbound provider-aws-dynamodb Table exposes
ttl.