feat: update demo to run child devices using tedge-agent #94
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Reuben Miller <reuben.d.miller@gmail.com>
Signed-off-by: Reuben Miller <reuben.d.miller@gmail.com>
Signed-off-by: Reuben Miller <reuben.d.miller@gmail.com>
reubenmiller
temporarily deployed
to
Test Pull Request
GitHub Actions
Inactive
Robot Results
|
Signed-off-by: Reuben Miller <reuben.d.miller@gmail.com>
reubenmiller
force-pushed
the
feat-replace-child-device-demo
branch
from
cc8dd2c to
531384a
Compare
reubenmiller
temporarily deployed
to
Test Pull Request
GitHub Actions
Inactive
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Promote the fact that the tedge-agent can also be run on child devices so that users don't need to develop there own custom agents to manage child devices (which run a Linux OS or as a container)
The main demo now has the following setup:
An example
firmware_updateworkflow has also been added to the main and child devices however it won't be visible until thin-edge.io 1.3.1 is release (due to thin-edge/thin-edge.io#3145)