feat: REST API to update entity twin data#3425
Conversation
Codecov ReportAttention: Patch coverage is 📢 Thoughts on this report? Let us know! 🚀 New features to boost your workflow:
|
Robot Results
|
57d1501 to
7f8012a
Compare
7f8012a to
e8a524c
Compare
didier-wenzek
left a comment
There was a problem hiding this comment.
- It would be good to implement
tedge http patchalong this PR. - I was expecting the updated twin data to be published over the
twintopics.
I pushed a commit for that: 4e3e940 |
4e3e940 to
6e7c4c6
Compare
Resolved by 6e7c4c6 |
Oops, this commits has been removed by |
didier-wenzek
left a comment
There was a problem hiding this comment.
I will be happy to merge this PR. However, I have first to re-push the commit adding support for tedge http patch.
| }, | ||
| } | ||
| ``` | ||
| * 400: Bad Request |
There was a problem hiding this comment.
I would give a bit more context on these errors, even if one can guess it.
Done: bece5bc |
reubenmiller
left a comment
There was a problem hiding this comment.
Nice feature.
As discussed, we could build upon this interface and also look at providing a similar API endpoint which mirrors the MQTT twin topic (te/{topic-id}/twin/{type}) as this would make it easier for users to switch between the MQTT and HTTP interfaces.
didier-wenzek
left a comment
There was a problem hiding this comment.
Approved. Thin-edge registration over HTTP is now a thing. Nice!
Signed-off-by: Didier Wenzek <didier.wenzek@free.fr>
bece5bc to
89c2e3c
Compare
Proposed changes
REST API to update entity twin data
Types of changes
Paste Link to the issue
Checklist
cargo fmtas mentioned in CODING_GUIDELINEScargo clippyas mentioned in CODING_GUIDELINESFurther comments