mirror of https://github.com/NVIDIA/OpenShell.git synced 2026-10-27 07:03:17 +08:00

Files

T

Simon Scatton 1959ea19be build(bazel): establish RFC 0012 Rust reference graph (#2414 )

Establish the Phase 1 reference implementation proposed by RFC 0012
while retaining the existing Cargo and Mise workflows during evaluation.

- pin Bazel 9.1.1 and configure Bzlmod, rules_rs, LLVM, protobuf, and
  Rust 1.95 toolchains
- import third-party crates from Cargo metadata and propagate the
  workspace version into Bazel targets
- add library, binary, proc-macro, unit-test, and integration-test
  targets across the supported Rust workspace crates and drivers
- generate protobuf Rust sources and descriptor sets under Bazel while
  preserving Cargo-compatible generated-code imports
- annotate aws-lc-sys and zstd-sys native dependencies, build Z3 4.15.2
  from source, and generate z3-sys bindings
- make CLI and procfs test fixtures available as explicit Bazel inputs
  without relying on fixed host binary paths
- define optimized release targets for Linux x86_64 and aarch64 CLI,
  sandbox, and gateway binaries, plus macOS aarch64 artifacts
- add Bazel, buildifier, and lcov to the Nix development environment

RFC: 0012 (rfc12 branch)
Refs: #2491

Signed-off-by: Simon Scatton <sscatton@nvidia.com>

2026-08-03 09:05:40 +00:00

src

refactor(policy): extract shared L7 endpoint validation (#2389 )

2026-07-24 17:48:24 +00:00

BUILD.bazel

build(bazel): establish RFC 0012 Rust reference graph (#2414 )

2026-08-03 09:05:40 +00:00

Cargo.toml

refactor(policy): extract shared L7 endpoint validation (#2389 )

2026-07-24 17:48:24 +00:00

README.md

docs(architecture): reset subsystem docs (#1184 )

2026-05-07 08:59:02 -07:00

README.md

openshell-providers

Provider discovery and normalization for credentials that sandboxes need at runtime.

The gateway persists provider records. The sandbox supervisor fetches resolved provider environment from the gateway and injects credentials into agent child processes. This crate keeps provider-specific discovery and normalization logic out of the CLI and gateway control flow.

Responsibilities

Discover local credentials from environment variables and known config files.
Normalize discovered data into provider records.
Keep provider-specific parsing rules in provider modules.
Avoid logging credential values.

Non-Responsibilities

Persisting provider records.
Authorizing provider CRUD operations.
Injecting credentials into sandbox child processes.
Routing inference requests.

Those are owned by the gateway, sandbox supervisor, and router.

Security Notes

Provider data often contains API keys, bearer tokens, or local account configuration. Discovery code should return structured values without printing or tracing secrets. Callers that display provider data must redact sensitive fields by default.