Hi Sai,
If by onboarding you mean the event when the device is first recognized by the system and registers itself, then we have a specific hook for it:
If you are compiling from master or using the builds from
downloads.openwisp.io, you can also use the new hotplug events:
That will allow you to add any logic you need.
For example, you could deploy scripts via OpenWISP templates, hook them to the post config reload event, which is triggered after the new config has been applied, and execute the scripts. In case you need the scripts to run only once you just need to write a control file somewhere in the permanent flash storage (eg: /etc/openwisp) and check whether that file exists before doing anything, if it exists, you simply exit, if it doesn't you let the script proceed.
It may sound obvious to some but I need to reiterate that I highly recommend to try this manually first and only once you are 100% sure that the scripts you prepared work, only then put those scripts in OpenWISP as templates and test the full flow.
Some people try to do it all at once and end up bombarding us with questions which most of the time do not have to do anything with OpenWISP but with their lack of understanding of OpenWrt.
Best regards
Federico CapoanoOpenWISP OÜ
Harjumaa, Tallinn, Sepapaja tn 6, 15551
VAT: EE101989729