Update/agent updater #3101
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!3101
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refs/pull/3101/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: #3103
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/3103
Original created: 2026-03-30T18:24:02Z
Original updated: 2026-03-30T18:29:47Z
Original head: carverauto/serviceradar:update/agent-updater
Original base: staging
Original merged: 2026-03-30T18:24:12Z by @mfreeman451
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
Imported GitHub PR review comment.
Original author: @Copilot
Original URL: https://github.com/carverauto/serviceradar/pull/3103#discussion_r3011499424
Original created: 2026-03-30T18:29:46Z
Original path: helm/serviceradar/templates/web.yaml
Original line: 250
DATASVC_ENABLED is now hardcoded to "true" for web-ng, which removes the ability to disable the supervised DataService.Client via chart values and changes behavior for existing installs. Consider wiring this to an explicit Helm value (or gating off .Values.kv.enabled / a new webNg.datasvc.enabled flag) so operators can disable datasvc client startup when datasvc is not deployed or connectivity is intentionally not configured.
Imported GitHub PR review comment.
Original author: @Copilot
Original URL: https://github.com/carverauto/serviceradar/pull/3103#discussion_r3011499460
Original created: 2026-03-30T18:29:46Z
Original path: elixir/serviceradar_core/lib/serviceradar/data_service/client.ex
Original line: 112
with_channel/2 sets connect_timeout_ms to the overall request timeout when falling back to a direct connection. That can make a single operation block significantly longer than expected (GenServer call timeout + connect timeout + RPC timeout) and diverges from the configured DATASVC_CONNECT_TIMEOUT_MS behavior. Prefer letting connect/1 use its configured/default connect_timeout_ms (or using a bounded min(timeout, default_connect_timeout)).
Imported GitHub PR review comment.
Original author: @Copilot
Original URL: https://github.com/carverauto/serviceradar/pull/3103#discussion_r3011499478
Original created: 2026-03-30T18:29:46Z
Original path: CHANGELOG
Original line: 5
Heading has a typo: "Whats New" should be "What's New".
Imported GitHub PR review comment.
Original author: @Copilot
Original URL: https://github.com/carverauto/serviceradar/pull/3103#discussion_r3011499495
Original created: 2026-03-30T18:29:47Z
Original path: elixir/serviceradar_core/test/serviceradar/data_service/client_test.exs
Original line: 10
This test assumes the supervised DataService.Client process is not running. That can become environment-dependent if DATASVC_HOST/PORT/ADDRESS are set (datasvc_connectivity_configured?/0 enables datasvc even in :test) or if other tests start the application, which would make Process.whereis(Client) non-nil and fail the assertion. To keep it deterministic, consider making the test non-async and explicitly forcing DATASVC_ENABLED to "false" for the test (with on_exit cleanup), or otherwise isolating the scenario where the client is guaranteed not to be started.