Repository navigation
Allow camera inputs to be deleted without losing plate history - #65
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Camera Inputs had no way to remove a configured camera. Add Delete input in the Actions column and configuration form for Axis, registered Blue Iris, and automatically discovered Blue Iris inputs, with a named confirmation dialog and keyboard focus handling.
Deleting an input stops imports, revokes its HTTP credential, retires its live MQTT subscription, and cancels queued detections and unfinished passages. Saved plate history, direction observations, and plate/scene images remain available. Archived identities prevent deleted cameras from being rediscovered from history; adding the same camera again creates a fresh input ID and credential. Shared brokers and other inputs are preserved.
The admin-only DELETE API waits for in-flight Axis processing before completing. Add a new checksummed migration with partial unique indexes so deleted names/device identities can be reused without changing prior migrations, and document the deletion/reconnection behavior.
Prepare Community 0.1.62, User Guide 3.30, changelog, roadmap, and current installation/update guidance.
Validation:
Release verification: all PR checks and main-branch CI, security and health checks passed. The main Windows native ReID test process initially exited with 0xC000001D; diagnostics were retained and the failed Windows job passed on a fresh runner. Exact-tag stable Windows packaging, all three CPU model probes, native PostgreSQL/ingestion and prior-release logical migration checks passed. All 3,361 update ZIP files, installer metadata, SQL sources, guide and 12 uploaded GitHub asset digests were verified. Independently downloaded Linux script checksums and public Windows updater discovery passed. Published Community 0.1.62: https://github.com/prsmith777/ALPR-Database-Community/releases/tag/v0.1.62