Open darylweir opened 1 year ago
@darylweir thank you for this report. I agree it would make sense for table_exists
to also allow .updating
. But there's probably also a use case (eg our test suite) for table_active
that mirrors the behavior of the current table_exists
. I'd be happy to accept a PR that improves this situation.
We use
Table.exists
as part of a health check for the containers in our application, which in turn callsClient.table_exists
. Today we had a short outage when all health checks began failing. It turned out the Dynamo table had enteredUPDATING
status.The implementation does the following:
This feels like a bug to us:
UPDATING
is a valid state while a variety of operations are being applied to the table. So the code should doreturn description.status in [TableStatus.active, TableStatus.updating]
.Thoughts?