v0.1.1
Fixed
DynamoDB
CreateTablereturnedResourceInUseExceptionwhen a previous failed attempt left an orphan directory — table existence is now determined by the presence of the.table.jsonmetadata file, not the directoryCreateTablecan now reuse an orphan directory left by a failed prior attempt instead of failing with a directory-exists errorListTablesincluded orphan directories (no.table.json) in its output, causingDescribeTableto returnResourceNotFoundExceptionfor the same nameListTablessilently swallowed non-ErrNotExistI/O errors fromstat; these are now propagated to the callerTransactWriteItemsdid not roll back writes already applied to disk when a later write in Phase 2 failed, violating atomicity; each item's pre-write state is now snapshotted and restored in reverse order on failure
Full Changelog: https://github.com/optiflowic/kumolo/blob/main/CHANGELOG.md