You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When working with DynamoDB, some users prefer to create the DynamoDB externally (with IAC for example).
Current Flow:
Try create table
Check type: if error.Type == ResourceInUseException then table exists and it's ok dismiss error.
else:... handle error.
The problem:
Even when working with an existing DDB table the code requires to have excessive permissions (CreateTable, DeleteTable and UpdateTable).
If the user did not provide those extra permissions it will be a different error than ResourceInUseException which causes the flow to fail.
Suggested solutions:
Could be that user indicates in the config that it's an existing table and the code will skip CreateTableWithContext.
Another option is to try and DescribeTable before trying to create it, the downside here is that it will cause initial error in cases the table doesn't exist.
Another option could be check if the error is Permission related and try to describe the table, only if the table does not exist handle this as real error.
The text was updated successfully, but these errors were encountered:
When working with DynamoDB, some users prefer to create the DynamoDB externally (with IAC for example).
Current Flow:
if error.Type == ResourceInUseException
then table exists and it's ok dismiss error.else:...
handle error.The problem:
Even when working with an existing DDB table the code requires to have excessive permissions (CreateTable, DeleteTable and UpdateTable).
If the user did not provide those extra permissions it will be a different error than
ResourceInUseException
which causes the flow to fail.Suggested solutions:
Could be that user indicates in the config that it's an existing table and the code will skip
CreateTableWithContext
.Another option is to try and
DescribeTable
before trying to create it, the downside here is that it will cause initial error in cases the table doesn't exist.Another option could be check if the error is Permission related and try to describe the table, only if the table does not exist handle this as real error.
The text was updated successfully, but these errors were encountered: