feat(core): scaffold edge onboarding service and APIs #2392
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!2392
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refs/pull/2392/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: #1904
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/1904
Original created: 2025-10-28T22:35:53Z
Original updated: 2025-10-29T04:46:43Z
Original head: carverauto/serviceradar:1903-secure-edge-poller-onboarding-flow
Original base: main
Original merged: 2025-10-29T04:46:41Z 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: @github-advanced-security[bot]
Original URL: https://github.com/carverauto/serviceradar/pull/1904#discussion_r2471455106
Original created: 2025-10-29T00:54:18Z
Original path: web/src/app/api/admin/edge-packages/helpers.ts
Original line: 33
Server-side request forgery
The URL of this request depends on a user-provided value.
The URL of this request depends on a user-provided value.
Show more details
Imported GitHub PR review comment.
Original author: @github-advanced-security[bot]
Original URL: https://github.com/carverauto/serviceradar/pull/1904#discussion_r2471455109
Original created: 2025-10-29T00:54:18Z
Original path: web/src/app/api/admin/edge-packages/helpers.ts
Original line: 68
Server-side request forgery
The URL of this request depends on a user-provided value.
The URL of this request depends on a user-provided value.
Show more details
Imported GitHub PR comment.
Original author: @gitguardian[bot]
Original URL: https://github.com/carverauto/serviceradar/pull/1904#issuecomment-3459591029
Original created: 2025-10-29T04:35:04Z
️✅ There are no secrets present in this pull request anymore.
If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.