Add Redis data management CLI

[scotte]

Maybe I'm just missing something? When using redis for persistence there is no way that I know of to manage (specifically delete for now, but maybe more) marks/etc which are sent to taky - and deleting them in the atak client does not delete them on the server (I have no idea if this is a general limitation with COT or not). Markers can be changed on the atak client, and those changes are propagated to server and other clients, but not deletions. As a result, every time an atak client connects to the server, all marks get retrieved.

I don't know if there are other object types that have this similar behavior. Position information seems to have an expiration time so it doesn't happen there.

There is no expectation of a fancy UI here, but a simple CLI to display and delete stored markers seems like it would be useful. Obviously redis-cli can be used here, but requires a bit more work to weed through the keys. Anyway, tossing this into the backlog and maybe I'll implement it as time allows.

[tkuester]

Awesome that you're using this feature! I thought it was a little underappreciated. ;) As of right now, there's no way to delete COTs through the CLI, but if you're using redis as a backend, you should be able to use `redis-cli del` and delete the cot by hand. I think one of the reasons I chose not to implement this (yet) was... 1. The redis-cli delete option should work out of the box 2. At the time of 0.10, the "server push delete notification" thing was still new-ish, and I didn't know how to use it yet. If you can help me get the structure of the COT message that tells clients to delete a COT, I'd be happy to (eventually) start integrating that feature!

…

On Mon, Jan 6, 2025 at 11:53 AM Scott E ***@***.***> wrote: Maybe I'm just missing something? When using redis for persistence there is no way that I know of to manage (specifically delete for now, but maybe more) marks/etc which are sent to taky - and deleting them in the atak client does not delete them on the server (I have no idea if this is a general limitation with COT or not). Markers can be changed on the atak client, and those changes are propagated to server and other clients, but not deletions. As a result, every time an atak client connects to the server, all marks get retrieved. I don't know if there are other object types that have this similar behavior. Position information seems to have an expiration time so it doesn't happen there. There is no expectation of a fancy UI here, but a simple CLI to display and delete stored markers seems like it would be useful. Obviously redis-cli can be used here, but requires a bit more work to weed through the keys. Anyway, tossing this into the backlog and maybe I'll implement it as time allows. — Reply to this email directly, view it on GitHub <#108>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQVTM5QI4URY3KAX62ZPXT2JKYJPAVCNFSM6AAAAABUV7H2WSVHI2DSMVQWIX3LMV43ASLTON2WKOZSG43TCMBVGMZDCNY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>