Content packages
A bundle can carry Netos content packages, such as netbox-rbac (groups and object permissions). Bundle verification checks every package file against SHA256SUMS.
On the NetBox host, run as root from the extracted bundle:
./netos-install packages list --site /root/netos/site.yml
./netos-install packages status --site /root/netos/site.yml --json
./netos-install packages install netbox-rbac --site /root/netos/site.yml
./netos-install packages install netbox-rbac --site /root/netos/site.yml --dry-run
You can also set content_packages: [netbox-rbac] in site.yml to apply it after the plugin post-check during install. A package install requires an existing successful Netos install and a valid licence. It verifies the bundle signature and hashes, takes a package snapshot, runs the bundled preflight against the installed netos-core, provisions the local deploy identity, then runs the bundled transactional importer as netbox. Package receipts are in the site's log_dir/packages/; command logs and snapshots use the installer's existing locations. On partial failure, use the printed rollback command with the exact site and package snapshot. A dry run makes no deployment changes: it takes no snapshot, creates no deploy identity, and writes no package receipt. It still writes a command log and receipt.
The offline path imports the package rows directly and starts no data pipelines. Its dashboard check needs HTTP, so the installer logs it as SKIP, never as PASS.