-
Notifications
You must be signed in to change notification settings - Fork 115
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
Ensure that config.json is always pretty printed #1300
Comments
@afitzek I think the main place where the config is generated is in the image maker as that injects the config. The OS should write/modify it with this pretty format. |
agherzan
pushed a commit
that referenced
this issue
Nov 29, 2018
Fixes #1300 Change-type: patch Signed-off-by: Andrei Gherzan <andrei@balena.io>
4 tasks
ghost
assigned agherzan
Nov 29, 2018
ghost
added
the
flow/in-review
label
Nov 29, 2018
agherzan
pushed a commit
that referenced
this issue
Nov 29, 2018
Fixes #1300 Change-type: patch Signed-off-by: Andrei Gherzan <andrei@balena.io>
This was referenced Nov 29, 2018
@afitzek All the components in the OS are now fixed to produce pretty formatted config.json. The only remaining one is the supervisor which has its own ticket: balena-os/balena-supervisor#816. Closing. |
ghost
removed
the
flow/in-review
label
Dec 5, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We decided to pretty print the config.json always, because customers did manually edit it, and stored non valid json, which corrupted the device. This should help them to keep a valid json.
Front conversations
The text was updated successfully, but these errors were encountered: