-
Notifications
You must be signed in to change notification settings - Fork 28
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
Document the choices of OTA operations #670
Conversation
Docs for 9e0a9a8 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2576/docs/artifacts/html/index.html |
This is not always the desired operation. There are 3 ways to control this operation | ||
|
||
1. Callbacks | ||
2. aktualizr-lite manual command line interface (Client) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we decided not to advertise that for now?
Maybe we can drop this and focus on custom sota x callbacks and check our customer feedback.
step through the install process. Unlike the callback method, this uses return codes to provice the status and | ||
does not perform the reboot of the device automatically. | ||
|
||
.. _`manual mode`: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment here, we were always against running manual commands as we cannot test every single interaction (we also changed our docs a while ago stating this is not supported and not recommended).
Thank you @Tim-Anderson for the help with this. I would say to remove CLI stuff until we have a chance to discuss with Mike/Mike Sul. Callbacks docs is what we are lacking at the moment. |
Docs for ae95aac are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2580/docs/artifacts/html/index.html |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Style/grammar suggestions, otherwise it lgtm
@Tim-Anderson What are we missing on this? |
@vanmaegima I have no problem including this in v93 if it is ready then. |
Docs for 91074ce are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2624/docs/artifacts/html/index.html |
Docs for e2d5f3f are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2627/docs/artifacts/html/index.html |
Signed-off-by: Tim Anderson <[email protected]>
Docs for ce42220 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2628/docs/artifacts/html/index.html |
LGTM |
Readiness
Overview
Why merge this PR? What does it solve?
Checklist
Optional. Add a 'x' to steps taken.
You can fill this out after opening the PR. "Did I..."
make linkcheck
.-s, --signoff
).-S, --gpg-sign
).Comments
Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.