-
Notifications
You must be signed in to change notification settings - Fork 54
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 child device firmware update support #1696 #1842
Document child device firmware update support #1696 #1842
Conversation
Robot Results
Passed Tests
|
@@ -28,3 +28,4 @@ | |||
26. [How to enable configuration management on child devices](./child_device_config_management_agent.md) | |||
27. [How to remotely connect to your thin-edge.io device via SSH/VNC/Telnet with Cumulocity remote access](./027_remote_access_with_cumulocity.md) | |||
28. [How to monitor a service from Cumulocity](./028_c8y_service_monitoring.md) | |||
29. [How to enable firmware management on child devices](./child_device_firmware_management.md) |
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.
This is okay for that PR to simply append the new Howto at the end the howto list. However, once merged the layout refactoring PR it will be important to group howtos along topics and to have this list in sync with SUMMARY.md that gives the page order.
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 will fix that merging the layout refactoring PR.
managing firmware file downloads, which are typically large files, even over flaky networks, | ||
caching the downloaded files for re-use across multiple child devices etc. | ||
|
||
But, an additional piece of software must be developed by the child device owner as well, |
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.
But sounds a bit negative. I would rather stress that this additional piece of software gives the user the ability to address the specifics of his device.
But, an additional piece of software must be developed by the child device owner as well, | |
In order to install the firmware itself on the child device, an additional piece of software must be developed by the child device owner, |
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.
Some need to be fixed before merge!
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.
Approved.
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.
Approved
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.
Approved. Thanks for the docs. We might consider adding a nice diagram in the future to help assist with the user's understanding, but we can consider that later.
25e4305
to
4c8474b
Compare
Proposed changes
Document firmware update support for child devices
Types of changes
Paste Link to the issue
Checklist
cargo fmt
as mentioned in CODING_GUIDELINEScargo clippy
as mentioned in CODING_GUIDELINESFurther comments