Page MenuHomePhabricator

[services] Tunnelbroker - Remove `ToDeviceID` index from messages table
ClosedPublic

Authored by max on Aug 1 2022, 7:05 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Nov 2, 5:29 PM
Unknown Object (File)
Oct 15 2024, 2:11 AM
Unknown Object (File)
Oct 7 2024, 3:38 PM
Unknown Object (File)
Oct 7 2024, 3:38 PM
Unknown Object (File)
Oct 7 2024, 3:38 PM
Unknown Object (File)
Oct 7 2024, 3:38 PM
Unknown Object (File)
Oct 7 2024, 3:36 PM
Unknown Object (File)
Sep 27 2024, 9:05 AM

Details

Summary

Because we've switched to the composite key in the messages table we don't need an additional index for a toDeviceID. We can use a hash_key.

Linear task: ENG-1493

Test Plan

Run yarn init-local-cloud is expected to be successful.

Diff Detail

Repository
rCOMM Comm
Branch
remove-ToDeviceID-index-messages
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

max held this revision as a draft.
This revision is now accepted and ready to land.Aug 2 2022, 8:59 AM

How do we keep this in sync with AWS cloud? Is the cloud recreated using the scripts or we do this by hand?

In D4695#135452, @tomek wrote:

How do we keep this in sync with AWS cloud? Is the cloud recreated using the scripts or we do this by hand?

We are doing this by hand in AWS and by yarn init-local-cloud to update the localstack.

Rebase and merge on master changes.

@max, is there a task tracking configuring Tunnelbroker in AWS via Terraform? If not, can you create one?

@max, is there a task tracking configuring Tunnelbroker in AWS via Terraform? If not, can you create one?

I think it's tracked for all services by ENG-1057

Can you create a new one specific to Tunnelbroker, assign it to yourself, add it as a related task to ENG-1057, and slot it in for Tunnelbroker 0.5?

In D4695#135515, @max wrote:
In D4695#135452, @tomek wrote:

How do we keep this in sync with AWS cloud? Is the cloud recreated using the scripts or we do this by hand?

We are doing this by hand in AWS and by yarn init-local-cloud to update the localstack.

this seems strange, we should just be running terraform apply to update the production stack in AWS