Page MenuHomePhabricator

[Tunnelbroker] Create undelivered messages table
ClosedPublic

Authored by jon on May 4 2023, 9:52 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Jul 17, 6:31 PM
Unknown Object (File)
Mon, Jul 1, 2:53 AM
Unknown Object (File)
Sat, Jun 29, 12:47 AM
Unknown Object (File)
Sat, Jun 29, 12:43 AM
Unknown Object (File)
Mon, Jun 24, 5:34 PM
Unknown Object (File)
Jun 22 2024, 5:25 PM
Unknown Object (File)
Jun 20 2024, 5:29 PM
Unknown Object (File)
Jun 20 2024, 8:30 AM
Subscribers

Details

Summary

Create dynamoDB table for storing undelivered
messages

Part of: https://linear.app/comm/issue/ENG-3823

Test Plan
# start localstack
comm-dev services start

# ensure that tunnelbroker-undelivered-messages table is created
cd services/terraform
./run.sh

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Harbormaster returned this revision to the author for changes because remote builds failed.May 4 2023, 10:07 AM
Harbormaster failed remote builds in B19048: Diff 26080!

Add createdAt as range_key

services/terraform/dynamodb.tf
101–104 ↗(On Diff #26132)

In other places, we use the RFC3339 string as a timestamp. Not sure if it is a good candidate for a range key though

jon added inline comments.
services/terraform/dynamodb.tf
101–104 ↗(On Diff #26132)

I just intend to use this to order the messages, so seconds from EPOCH seems like a simple yet effective way to achieve this.

This also avoids having to parse the date back in.

bartek added inline comments.
services/terraform/dynamodb.tf
101–104 ↗(On Diff #26132)

That makes sense, thanks for explaining

This revision is now accepted and ready to land.May 9 2023, 11:18 PM