-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trigger script after provision #107
Comments
Yes - a somewhat-trivial modification to the sb-provisioner script would perform the changes you want for now - but the intent is to introduce a range of hook-scripts at various points through the process to make this more straightforward. After
"${TMP_DIR}"/rpi-rootfs-img-mount , and you're free to make changes to your copy to facilitate your use case.
One warning, however - making changes there may foul the hot-path detection (which relies purely on sizes and file presence). In such a mode, you would likely want to not set RPI_SB_WORKDIR, and instead regenerate your provisioning asset for each device. |
Great, thankyou, I will try this and make sure I don't set the WORKDIR so that it regenerates on each provision. If I installed the sb-provisioner via apt where will I find the rpi-sb-provisioner.sh to edit? |
Installed from https://github.com/raspberrypi/rpi-sb-provisioner/blob/main/debian/install |
amazing, thank you |
Is there a way I could automate triggering a script after each provision? I would like to edit the hostname and add a linked deploy key to the image I am using. I am making the deploy keys on the provisioning device
The text was updated successfully, but these errors were encountered: