chore: pkg/db cleanup #749

New issue

Closed

opened 2026-03-28 04:28:08 +00:00 by mfreeman451 · 1 comment

mfreeman451 commented

2026-03-28 04:28:08 +00:00

Owner

Imported from GitHub.

Original GitHub issue: #2305
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2305
Original created: 2026-01-14T20:46:34Z

Not sure if we can completely remove pkg/db get, I think db-event-writer might use it, but we can certainly clean it up. Now that serviceradar-core (golang) has been fully removed we shouldn't need hardly any of this I would think.

Imported from GitHub. Original GitHub issue: #2305 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2305 Original created: 2026-01-14T20:46:34Z --- Not sure if we can completely remove `pkg/db` get, I think db-event-writer might use it, but we can certainly clean it up. Now that `serviceradar-core` (golang) has been fully removed we shouldn't need hardly any of this I would think.

mfreeman451 commented

2026-03-28 04:28:08 +00:00

Author

Owner

Imported GitHub comment.

Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2305#issuecomment-3771026524
Original created: 2026-01-20T04:49:10Z

a lot of this work has been done but still need to go through and verify, I think the intention is to keep db-event-writer at least in the near-term, and not replace it with something elixir based, so we can't get rid of pkg/db completely. closing as not planned for now.

Imported GitHub comment. Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2305#issuecomment-3771026524 Original created: 2026-01-20T04:49:10Z --- a lot of this work has been done but still need to go through and verify, I think the intention is to keep `db-event-writer` at least in the near-term, and not replace it with something elixir based, so we can't get rid of `pkg/db` completely. closing as not planned for now.