-
Notifications
You must be signed in to change notification settings - Fork 25
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
DynamoDB backups of deleted tables excluded #15
Comments
Ah, makes sense. I think moving ddb/backup to a separate resource type makes the most sense. It'd add a relation back to a potentially nonexistent table, but that should be fine? That is currently how RDS backups are handled (relationship goes to a non-existent database). I'll get that updated. |
This should be fixed in the latest version (v0.6.2). Let me know if it's still not correct |
Yeah that works perfectly! Having a semi-empty relationship when the DDB table is gone but backups still exist makes sense, since they really are orphaned resources. |
First, thanks for adding DDB backups to 0.6.1.
Commit 0925415... / issue #14 added DDB backups as sub-resources to
ddb/table
. DynamoDB backups can exist of now-deleted tables that still need to be cleaned up.To gather those, I think there needs to be a separate resource type
ddb/backup
added instead of backups being a sub-resource listed on existing tables. Another option would be to make a fakeddb/table
resource with a status ofDELETED
and put those backups as sub-resources of.The text was updated successfully, but these errors were encountered: