doc: Entity management API documentation#3659
Conversation
| @@ -1,11 +1,21 @@ | |||
| --- | |||
| title: Registration | |||
| title: Entity Management | |||
There was a problem hiding this comment.
Open to use any other title like Entity Lifecycle Management that covers CRUD operations on entities. Even the side-pane title (directory name) which is currently Registration could be changed accordingly.
There was a problem hiding this comment.
Entity Management is okay
There was a problem hiding this comment.
We should probably rename the folder then from "registration" to "entity-management"
There was a problem hiding this comment.
Will rename the folder right before the merge.
| @@ -83,158 +83,79 @@ GET /v1/entities/{topic-id} | |||
| curl http://localhost:8000/te/v1/entities/device/child01 | |||
| ``` | |||
|
|
|||
| ## Query entities | |||
There was a problem hiding this comment.
The diff of this file is a bit weird. All I did was to move this Query entities section to the end of this file so that the CRUD operations are placed together. This Query entities section was quite big and in the middle of them earlier, placed along with Fetch entities(as querying is also another kind of READ operation).
Codecov ReportAll modified and coverable lines are covered by tests ✅ 📢 Thoughts on this report? Let us know! 🚀 New features to boost your workflow:
|
| import DocCardList from '@theme/DocCardList'; | ||
|
|
||
| Managing registration and deregistration of child devices and services on %%te%%. | ||
| %%te%% provides two different API interfaces for managing entities on a device: |
There was a problem hiding this comment.
This introduction is missing something. The focus is on HTTP vs MQTT but the purpose of these APIs is a bit vague. I would give a short overview of these core functionality.
| %%te%% provides two different API interfaces for managing entities on a device: | |
| %%te%% provides an API for managing entities on a device: to register child devices and services with metadata describing their role and relationship. | |
| %%te%% provides two different flavor of this API: |
There was a problem hiding this comment.
Revamped this intro significantly in 4ff49e7, highlighting the pros and cons of both APIs
didier-wenzek
left a comment
There was a problem hiding this comment.
Not a single world is said about updating an entity over MQTT. It would be good to tell what the restrictions are.
|
|
||
| To demonstrate different query examples, the following entity tree is assumed as the base: | ||
|
|
||
| ``` |
There was a problem hiding this comment.
It might be more clear to users if we simplify the example a bit, e.g. only going 2 child devices deep, and using 1-2 services per device...not sure if we could also use some more realistic names, e.g. tedge-mapper-c8y, and tedge-agent on the main device?
9a6322b to
aebd479
Compare
Robot Results
|
Proposed changes
Types of changes
Paste Link to the issue
Checklist
just prepare-devonce)just formatas mentioned in CODING_GUIDELINESjust checkas mentioned in CODING_GUIDELINESFurther comments