| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Added key and value both in response so that user can know which key the value corresponds to.
The current persistence implementation responds with only the value when queried. Since this is
async call and multiple keys can be queried at the same time, the key and value should be given
as response to any persistence query done. This will improve the readability of the Read verb
response for user application.
Also made the same changes for failed case of Read verb so that if read verb fails, user can know
for which key it failed.
Bug-AGL: SPEC-2828
Signed-off-by: Gaykawadpk <Puja.Kumari@kpit.com>
Change-Id: I565cd78ca2c1e7c5d5f63ab49479b495044772ce
|
|
Bug-AGL: SPEC-2743
Change-Id: I7eb6c685076aafd9c685aea102ee91ae95c716f8
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
AFB_INFO calls for key creation/update/delete for key value pairs is
cluttering up the journal, and also a security risk for possibly leaking
data.
Change-Id: Ifcaf3de5551c66ba4e5813dcaf447d9ca1ef25a1
Signed-off-by: Matt Ranostay <matt.ranostay@konsulko.com>
|
|
Change-Id: I7103241843736e1a5747253781485afa457a64d0
Signed-off-by: Loïc Collignon <loic.collignon@iot.bzh>
|
Gaykawadpk
José Bollo
Matt Ranostay
Loïc Collignon