search

LiquidAI-project / wasmiot-orchestrator

MIT License
0 stars 1 forks source link

[CLOSED] 20. Add endpoint for getting the Wasm-file from orchestrator #22

Closed trkks closed 1 year ago

trkks commented 1 year ago 
Author  'juaatark'
Created 2023-03-15T13:58:00.531+02:00
Updated 2023-03-17T17:57:11.284+02:00
Closed  2023-03-17T17:57:11.274+02:00

The metadata (i.e., database entry) is currently available from the /file/module/:id route, but the actual executable .wasm needs also to be requestable by supervisors

trkks commented 1 year ago 
Author 'juaatark'
Originally created at 2023-03-15T14:15:37.093+02:00

Based on supervisor at this procedure this route should serve only the .wasm -filecontents themselves and on the other hand the metadata of all modules in a deployment (regarding this supervisor) would be POSTed beforehand by the orchestrator (i.e., at the time when orchestrator starts the deployment).

trkks commented 1 year ago 
Author 'juaatark'
Originally created at 2023-03-17T17:56:37.665+02:00

.wasm-serving endpoint /file/module/<id>/wasm done in 3329e65809f53220d0c5061200796b4daa59ceac

trkks commented 1 year ago 
Author 'juaatark'
Originally created at 2023-03-17T17:57:11.011+02:00

Sending info of all modules at once to device done in 7052534404d2c04553882f00937e0046045fd03b