azaion/loader
1
0
Fork 0
mirror of https://github.com/azaion/loader.git synced 2026-04-22 07:06:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove Jetson device provisioning runbook and scripts

Browse Source 
- Deleted the provisioning runbook and associated scripts as they have been relocated to the suite meta-repo. This change reflects the shift in focus for device provisioning, which is now managed outside the loader repository, streamlining the project and removing outdated documentation.
This commit is contained in:
Oleksandr Bezdieniezhnykh
2026-04-19 21:38:00 +03:00
parent ac6cb35112
commit ac9370931c
1 changed files with 0 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
_docs/02_document/deployment/provisioning_runbook.md
-14
View File
@@ -1,14 +0,0 @@
# Jetson device provisioning runbook (moved)
The provisioning runbook and its scripts (`provision_devices.sh`, `ensure_l4t.sh`, `setup_rootfs_docker.sh`, `harden_rootfs.sh`) no longer live inside the `loader` repository.
They were relocated to the suite meta-repo because device provisioning is a fleet/manufacturing concern, not a Loader concern — it sets up the base OS, Docker, identity, and hardening that all services share.
- **New location:** `suite/provisioning/`
- **Runbook:** `suite/provisioning/README.md`
If you are working inside the loader repo in isolation, the scripts are not available here; clone the suite meta-repo to run provisioning.
## Note on Loader retirement
The provisioning flow in `suite/provisioning/` still references Loader today because `setup_rootfs_docker.sh` has not yet been rewritten for the Scenario X deployment model (Watchtower + rclone + flight-gate). The rewrite is tracked as a follow-up in `suite/ci/README.md`. Until the rewrite lands, newly-provisioned devices continue to boot with the legacy Loader service and will need a separate migration step to the new deployment model.