-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Observing DynamoDB Table rangeKey throws Unused attributes error #1597
Open
1 task done
Labels
Comments
Hi @chris-believer, Thank you for your clear and detailed issue report. I was able to reproduce the issue on my side as well:
This seems like something we need to investigate further. In the meantime, as a potential workaround, could you try importing the resource using the following approach?
|
turkenf
added
is:triaged
Indicates that an issue has been reviewed.
and removed
needs:triage
labels
Jan 2, 2025
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Is there an existing issue for this?
Affected Resource(s)
Resource MRs required to reproduce the bug
Steps to Reproduce
Table
with arangeKey
. This can be externally created or an orphaned crossplane created table after deletion from kubernetes.Table
withmanagementPolicies:["Observe"]
and the existingexternal-name
set.What happened?
Relevant Error Output Snippet
Crossplane Version
1.18.0
Provider Version
1.17.0
Kubernetes Version
v1.30.6-eks-7f9249a
Kubernetes Distribution
EKS
Additional Info
rangeKey
elements in alocalSecondaryIndex
, but pulled them out during troubleshooting to get a smaller reproduction. TherangeKey
attributes are also marked as Unused. I did not testglobalSecondaryIndex
but suspect it would error as well.The text was updated successfully, but these errors were encountered: