autonomy ros2 bridge

Manage the governed_ros2_bridge native binary

Synopsis

Manage the governed_ros2_bridge C++ executable that the native
--force-native --governed-bridge launch path depends on.

The bridge ships only inside the demo container image by default; for
the native path, operators install it from the release pipeline's
tarballs (or build it from source via scripts/install-governed-bridge.sh).

Subcommands:

  install  — fetch the right tarball for the host's ROS distro + arch,
             cosign + SHA256 verify, install to /usr/local/bin
             (or --install-dir).

Options inherited from parent commands

      --require-signed-manifest   Refuse to start if the SHA256SUMS release manifest or its cosign signature is missing/invalid (Tier 2 binary-integrity check; default: build-time compile-in via -ldflags -X, build-hardened artifacts=true, all others=false)

Subcommands

See also

  • autonomy ros2 — Execute governed ROS2 commands under AutonomyOps policy