luci-app-attendedsysupgrade/auc: custom uci-defaults support
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 450
- Forks
- 111
- PR merge metrics
- No merged PRs in 30d
Description
uci-defaults scripts are essential for accessing device after firmware reset.
If user defined a custom UCI-Defaults script with OpenWrt Firmware Selector, it's feasible to preserve it upon firmware upgrade, at least optionally, and include it to new image.
Otherwise, access to the device can be lost next time user performs firmware Reset.
As a simple approach to solve this, luci-app-attendedsysupgrade/auc utilities could check if /rom/etc/uci-defaults/99-asu-defaults file exists in current firmware,
https://github.com/openwrt/asu/blob/3ef4757b9fcc401b3d18ebb6954276b0210f07fb/asu/build.py#L202
and if so, include it to a new image using "defaults" BuildRequest member:
https://sysupgrade.openwrt.org/ui/
BuildRequest {
defaults string Custom shell script embedded in firmware image to be run on first boot.
@aparcar @mwarning @dangowrt
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the luci-app-attendedsysupgrade/auc utilities and the referenced asu/build.py section around line 202. Inspect how BuildRequest handles the defaults member, then verify that an existing /rom/etc/uci-defaults/99-asu-defaults file is included in the generated firmware image and runs on first boot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100