Feature #640

imrest should provide a configuration API

Added by Hammel about 1 year ago. Updated about 1 year ago.

Status:NewStart date:12 Jul 2018
Priority:ImmediateDue date:
Assignee:Hammel% Done:

0%

Category:Software
Target version:Iron Man - 002 - MVP
Severity:03 - Medium

Description

This could be used by PiBoxd to query for where the IoT device registration directory can be found.

There is already the /monitor API. This needs to be extended to /monitor/{config,descriptor}.

The API should test if the request comes from internally (the localhost) or from externally. Only internal requests should be honored.

The API should provide the following information:
  • PairEnabledStamp
  • ironmanDir
  • monitorDir
  • iotDir
  • stampDir
  • uuid (monitor's uuid)

This should all be returned in a JSON packet.

When this is implemented, update the piboxd's iot.c code to use it instead of using the hard-coded path to the iotDir and update Jarvis to use the /monitor/descriptor API instead of just /monitor.

History

#1 Updated by Hammel about 1 year ago

  • Description updated (diff)

#2 Updated by Hammel about 1 year ago

  • Description updated (diff)

Also available in: Atom PDF