fixing drift wip #2485
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!2485
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refs/pull/2485/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: #2028
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2028
Original created: 2025-11-28T01:26:51Z
Original updated: 2025-11-28T19:12:58Z
Original head: carverauto/serviceradar:bug/dire_device_drift
Original base: main
Original merged: 2025-11-28T19:07:15Z 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
Bug fix
Description
Prevent impossible promotion policies when fingerprinting disabled
Update all container image tags to new SHA for drift fix
Disable fingerprint requirement in Helm values configuration
Mark drift mitigation task as completed in tracking document
Diagram Walkthrough
File Walkthrough
config.go
Add fingerprint policy conflict validationpkg/core/config.go
RequireFingerprintwhen fingerprinting isdisabled
values.yaml
Update image tags and disable fingerprint requirementhelm/serviceradar/values.yaml
(sha-13d9cc627541190980bbad253ae6b3484a2648a0)
requireFingerprintfrom true to false in promotionconfiguration
tasks.md
Mark drift mitigation task as completedopenspec/changes/add-identity-reconciliation-engine/tasks.md
Imported GitHub PR comment.
Original author: @qodo-code-review[bot]
Original URL: https://github.com/carverauto/serviceradar/pull/2028#issuecomment-3587645898
Original created: 2025-11-28T01:27:19Z
You are nearing your monthly Qodo Merge usage quota. For more information, please visit here.
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: Meaningful Naming and Self-Documenting Code
Objective: Ensure all identifiers clearly express their purpose and intent, making code
self-documenting
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: Comprehensive Audit Trails
Objective: To create a detailed and reliable record of critical system actions for security analysis
and compliance.
Status:
Missing auditing: New configuration mutation disabling
cfg.Promotion.RequireFingerprintoccurs without anyaudit/log entry recording who/what triggered the change and its outcome.
Referred Code
Generic: Robust Error Handling and Edge Case Management
Objective: Ensure comprehensive error handling that provides meaningful context and graceful
degradation
Status:
Silent auto-fix: The code auto-disables
RequireFingerprintwhen fingerprinting is disabled withoutsurfacing a warning or error, which may hide configuration mistakes and reduce
observability.
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/2028#issuecomment-3587646851
Original created: 2025-11-28T01:28:16Z
You are nearing your monthly Qodo Merge usage quota. For more information, please visit here.
PR Code Suggestions ✨
Explore these optional code suggestions:
Decouple service image updates from fixes
The PR combines a logic fix in the
coreservice with a mass update of allcontainer image tags. It is suggested to decouple these changes by only updating
the image for the affected service to reduce deployment risk.
Examples:
helm/serviceradar/values.yaml [5-27]
pkg/core/config.go [284-287]
Solution Walkthrough:
Before:
After:
Suggestion importance[1-10]: 7
__
Why: The suggestion correctly identifies a risky practice of bundling a specific service fix with a fleet-wide image update, which increases deployment complexity and risk.
✅
Use YAML anchors for image tagsSuggestion Impact:
The commit added an appTag anchor and replaced repeated image tags with references (*appTag) for most services, reducing duplication.code diff:
Use YAML anchors in
values.yamlto define the common image tag once and reuse itacross multiple services, improving maintainability.
helm/serviceradar/values.yaml [4-27]
[Suggestion processed]Suggestion importance[1-10]: 7
__
Why: The suggestion improves the maintainability of the Helm
values.yamlfile by using YAML anchors to avoid repeating the same image tag, reducing the risk of human error during updates.✅
Log when configuration is silently changedSuggestion Impact:
A warning log line was added before setting RequireFingerprint to false when fingerprinting is disabled, matching the suggestion.code diff:
Add a warning log when
RequireFingerprintis automatically set tofalsetonotify operators of the configuration override.
pkg/core/config.go [284-287]
[Suggestion processed]Suggestion importance[1-10]: 6
__
Why: The suggestion correctly identifies that silently changing a configuration can be confusing and improves observability by adding a log message, which is a good practice for maintainability.