cleanup removed web #2648
No reviewers
Labels
No labels
1week
2weeks
Failed compliance check
IP cameras
NATS
Possible security concern
Review effort 1/5
Review effort 2/5
Review effort 3/5
Review effort 4/5
Review effort 5/5
UI
aardvark
accessibility
amd64
api
arm64
auth
back-end
bgp
blog
bug
build
checkers
ci-cd
cleanup
cnpg
codex
core
dependencies
device-management
documentation
duplicate
dusk
ebpf
enhancement
eta 1d
eta 1hr
eta 3d
eta 3hr
feature
fieldsurvey
github_actions
go
good first issue
help wanted
invalid
javascript
k8s
log-collector
mapper
mtr
needs-triage
netflow
network-sweep
observability
oracle
otel
plug-in
proton
python
question
reddit
redhat
research
rperf
rperf-checker
rust
sdk
security
serviceradar-agent
serviceradar-agent-gateway
serviceradar-web
serviceradar-web-ng
siem
snmp
sysmon
topology
ubiquiti
wasm
wontfix
zen-engine
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
carverauto/serviceradar!2648
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refs/pull/2648/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Imported from GitHub pull request.
Original GitHub pull request: #2245
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2245
Original created: 2026-01-11T18:00:21Z
Original updated: 2026-01-11T18:02:00Z
Original head: carverauto/serviceradar:chore/remove-legacy-agent
Original base: testing
Original merged: 2026-01-11T18:00:56Z by @mfreeman451
User description
IMPORTANT: Please sign the Developer Certificate of Origin
Thank you for your contribution to ServiceRadar. Please note, when contributing, the developer must include
a DCO sign-off statement indicating the DCO acceptance in one commit message. Here
is an example DCO Signed-off-by line in a commit message:
Describe your changes
Issue ticket number and link
Code checklist before requesting a review
PR Type
Enhancement
Description
Remove legacy Next.js web application and all associated artifacts
Clean up Makefile targets and build system references to deprecated web
Update documentation to remove legacy UI configuration details
Archive change specification documenting complete legacy web removal
Diagram Walkthrough
File Walkthrough
1 files
Remove legacy web build targets and dependencies5 files
Remove deprecated Next.js UI documentationUpdate requirements to reflect complete legacy removalArchive modified requirements for legacy web removalArchive completed tasks for legacy web cleanupArchive change proposal for legacy web removal101 files
Imported GitHub PR comment.
Original author: @qodo-code-review[bot]
Original URL: https://github.com/carverauto/serviceradar/pull/2245#issuecomment-3735204724
Original created: 2026-01-11T18:01:00Z
PR Compliance Guide 🔍
Below is a summary of compliance checks for this PR:
No security concerns identified
No security vulnerabilities detected by AI analysis. Human verification advised for critical code.🎫 No ticket provided
Codebase context is not defined
Follow the guide to enable codebase context checks.
Generic: Comprehensive Audit Trails
Objective: To create a detailed and reliable record of critical system actions for security analysis
and compliance.
Status: Passed
Generic: Robust Error Handling and Edge Case Management
Objective: Ensure comprehensive error handling that provides meaningful context and graceful
degradation
Status: Passed
Generic: Secure Error Handling
Objective: To prevent the leakage of sensitive system information through error messages while
providing sufficient detail for internal debugging.
Status: Passed
Generic: Secure Logging Practices
Objective: To ensure logs are useful for debugging and auditing without exposing sensitive
information like PII, PHI, or cardholder data.
Status: Passed
Generic: Security-First Input Validation and Data Handling
Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent
vulnerabilities
Status: Passed
Generic: Meaningful Naming and Self-Documenting Code
Objective: Ensure all identifiers clearly express their purpose and intent, making code
self-documenting
Status:
Misleading target name: The
deb-all-containerMakefile target name and description imply container support, butthe updated commands no longer indicate container-related behavior, making the identifier
misleading.
Referred Code
Compliance status legend
🟢 - Fully Compliant🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label
Imported GitHub PR comment.
Original author: @qodo-code-review[bot]
Original URL: https://github.com/carverauto/serviceradar/pull/2245#issuecomment-3735207687
Original created: 2026-01-11T18:02:00Z
PR Code Suggestions ✨
Explore these optional code suggestions:
Update root AGENTS.md documentation
Update the
AGENTS.mdfile to remove the reference to the legacyweb/directoryin the "Repository Layout" section. This change ensures the documentation
accurately reflects the removal of the old UI.
Solution Walkthrough:
Before:
After:
Suggestion importance[1-10]: 7
__
Why: The suggestion identifies a relevant documentation file (
AGENTS.md) likely missed during the cleanup, and updating it is crucial for maintaining consistency with the PR's goal of removing all legacy artifacts.Add build prerequisite for agent
Add
build-binariesas a prerequisite to thedeb-agenttarget.Makefile [358]
Suggestion importance[1-10]: 7
__
Why: This is a valid suggestion that improves the robustness of the
Makefileby explicitly declaring a dependency, preventing potential build failures ifdeb-agentis run in isolation.