Closed rina23q closed 10 months ago
Resolved by #2464
To try the message conversion, one needs to enable firmware_update
feature by tedge config
, then restart tedge-mapper-c8y
.
sudo tedge config set c8y.enable.firmware_update true
QA has thoroughly checked the feature and here are the results:
Is your feature improvement request related to a problem? Please describe. As a part of making all c8y-*-plugins generic, c8y-firmware-plugin's feature should be converted to mapper, agent, and operation workflow. This ticket focuses on c8y-mapper side's implementation.
Describe the solution you'd like c8y-mapper addresses:
Command Metadata
Topic:
te/<identifier>/cmd/firmware_update
Payload: can be{}
empty JSON, orname
,version
,url
(all fields are optional)Upon receiving a message on the topic, c8y-mapper translates it to
c8y_Firmware
(SmartREST114
) by using file system supported operation management115
). Missing field will be reported as empty string.New Command
init
state. Topic:te/<identifier>/cmd/firmware_update/<cmd-id>
executing
state, c8y-mapper converts the message to SmartREST501
(operation executing).failed
orsuccessful
), c8y-mapper converts the message to SmartREST.503
(operation successful) and115
(current firmware)502
(operation failed)Describe alternatives you've considered
Additional context If user wants to use the old API by c8y-firmware-plugin,
firmware_update
feature support by tedge config from c8y-mapper.c8y-firmware-plugin
.