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
The CLI lets one provide a data file to use for the key value. Since everything is stored as binary in DynamoDB (and ultimately S3 and hopefully anything else that ends up being a storage engine) it's easy to do this.
However, API Gateway doesn't allow binary data to be sent through it. So that's a bummer - there wouldn't be parity between the local API server, the CLI, and then AWS API Gateway.
AWS is hopefully changing this in the future. I'm not sure it's worth exploring until they do. This isn't a huge issue or major use case.
The text was updated successfully, but these errors were encountered:
The CLI lets one provide a data file to use for the key value. Since everything is stored as binary in DynamoDB (and ultimately S3 and hopefully anything else that ends up being a storage engine) it's easy to do this.
However, API Gateway doesn't allow binary data to be sent through it. So that's a bummer - there wouldn't be parity between the local API server, the CLI, and then AWS API Gateway.
AWS is hopefully changing this in the future. I'm not sure it's worth exploring until they do. This isn't a huge issue or major use case.
The text was updated successfully, but these errors were encountered: