chore: adding alpine packages #2994
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!2994
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refs/pull/2994/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: #2953
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2953
Original created: 2026-03-01T00:10:37Z
Original updated: 2026-03-01T00:36:32Z
Original head: carverauto/serviceradar:1872-chore-add-additional-tools-to-serviceradar-tools-image
Original base: staging
Original merged: 2026-03-01T00:36:24Z 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
Add four new Alpine Linux packages to build system
Include inetutils-telnet, libcap2, libbsd, libmd APK files
Create extraction rules for each new package
Integrate new packages into alpine_netutils rootfs
Diagram Walkthrough
File Walkthrough
MODULE.bazel
Add Alpine package HTTP file definitionsMODULE.bazel
http_filerules for Alpine packagesBUILD.bazel
Add APK extraction rules and integrate packagesdocker/images/BUILD.bazel
genruletargets for extracting APK filespackages
formats
dependencies
Imported GitHub PR comment.
Original author: @qodo-code-review[bot]
Original URL: https://github.com/carverauto/serviceradar/pull/2953#issuecomment-3978676772
Original created: 2026-03-01T00:10:58Z
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.🎫 #1872
pingin theserviceradar-toolsimage by ensuring the requiredlibcap.so.2dependencyis present (and
pingruns without the shared-library relocation errors shown).required to support the above tooling.
serviceradar-toolsimage thattelnetexecutes successfullyand
pingruns withoutlibcap.so.2errors (runtime verification in the container).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: Meaningful Naming and Self-Documenting Code
Objective: Ensure all identifiers clearly express their purpose and intent, making code
self-documenting
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
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/2953#issuecomment-3978678732
Original created: 2026-03-01T00:12:07Z
PR Code Suggestions ✨
Explore these optional code suggestions:
✅
Refactor duplicated logic into a macroSuggestion Impact:
The four duplicated genrule definitions were removed and replaced by calls to a loaded macro (apk_rootfs_amd64), consolidating the shared shell logic into a single reusable definition.code diff:
Refactor the four new
genruletargets into a single Bazel macro to eliminateduplicated shell script logic and improve maintainability.
docker/images/BUILD.bazel [149-279]
[Suggestion processed]Suggestion importance[1-10]: 7
__
Why: The suggestion correctly identifies significant code duplication in the newly added
genruletargets and proposes an idiomatic Bazel solution by refactoring the logic into a macro, which greatly improves maintainability.✅
Unify tar extraction callSuggestion Impact:
The commit removed the duplicated genrule shell scripts containing the tar-extension case statement entirely, replacing them with a shared apk_rootfs_amd64 macro, thereby eliminating the need for the multi-branch tar extraction logic the suggestion targeted (though not by introducing the specific tar --auto-compress line in this diff).code diff:
Replace the
casestatement fortarextraction with a singletar --auto-compresscommand to simplify the logic.
docker/images/BUILD.bazel [162-167]
[Suggestion processed]Suggestion importance[1-10]: 5
__
Why: This is a good suggestion that simplifies the shell script by replacing a multi-branch
casestatement with a singletarcommand using--auto-compress, making the code more concise and easier to maintain.✅
Replace backticks with $(…)Suggestion Impact:
The commit removed the genrule shell snippets that contained backtick command substitutions (including the DATA_TAR assignment) by refactoring them into apk_rootfs_amd64 macro calls, thereby eliminating the backtick usage rather than directly converting it to $(...).code diff:
Replace backticks (
...) with the modern$(...)syntax for command substitutionin the shell script.
docker/images/BUILD.bazel [160]
[Suggestion processed]Suggestion importance[1-10]: 3
__
Why: The suggestion correctly points out that using
$(...)is preferred over backticks for command substitution, which is a good practice for shell script readability and robustness, although it is a minor style improvement.Imported GitHub PR comment.
Original author: @qodo-code-review[bot]
Original URL: https://github.com/carverauto/serviceradar/pull/2953#issuecomment-3978707969
Original created: 2026-03-01T00:30:09Z
CI Feedback 🧐
A test triggered by this PR failed. Here is an AI-generated analysis of the failure:
Action: build
Failed stage: Configure SRQL fixture database for tests [❌]
Failed test name: ""
Failure summary:
The action failed because a required secret/environment variable for the test/fixture setup was
missing:
- The job explicitly exited with:
SRQL_TEST_DATABASE_CA_CERT secret must be configured toverify SRQL fixture TLS.followed byProcess completed with exit code 1.(around lines 707-708).-
In the environment,
SRQL_TEST_DATABASE_CA_CERTis shown as empty, so the workflow halted beforerunning further steps.
An additional issue occurred during post-job cleanup:
-
fatal: No url found for submodule path'swift/FieldSurvey/LocalPackages/arrow-swift' in .gitmodulescaused a git command in cleanup to exit128 (lines 718-719), but the primary job failure is the missing
SRQL_TEST_DATABASE_CA_CERT.Relevant error logs: