-
Notifications
You must be signed in to change notification settings - Fork 324
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
[WIP] add checks for obsolete settings #1702
Conversation
Being visible only when |
@mweinelt where should it be visible? e.g. an error of the site config is visible via |
One option would be to make obsolete settings a hard failure. We currently don't have a good way to make warnings visible without |
hard failure should be OK as its easily fixable and clearly highlights something has to be done. |
running
with a
or with a
or a different obsolete setting '...' without a custom message will fail with
|
Implementation looks ok. I think the following formatting/wording would look better:
|
@NeoRaider i reworded the message somehow. Not sure if it is okay like it is now: 38a10d5 Should that be documented somewhere? Are there docs for check_site available? |
gluon-autoupdater: add site check for obsolete setting probability gluon-core: add site check for obsolete setting lede
This might fix #1698
When running
make V=s GLUON_RELEASE="master" GLUON_TARGET="ar71xx-tiny" GLUON_DEVICES="tp-link-tl-wr840n-v2"
(site conf of Freifunk Hamburg and Gluon master) the following output is printed eight times:I am not sure if
print()
is a good choice or if something likeio.stderr:write()
should be usede.g.
io.stderr:write(src .. ' obsolete: ' .. string.format(...) .. '\n')
(but it is visible withV=s
, only)Also not sure if a generic text is fine or if it should be possible to describe what is wrong, add a link to the documentation/release notes, ... what do you think?