firmware: start implementing deleteBlob
If a client sends a deleteBlob, two things should happen. The active
blob is cleared and the states are all reset, effectively like an abort.
Change-Id: I54f2986b7cad9b7fc117d36a8e631e84c8e8feb8
Signed-off-by: Patrick Venture <venture@google.com>
diff --git a/firmware_handler.cpp b/firmware_handler.cpp
index 3ce65aa..3545fd2 100644
--- a/firmware_handler.cpp
+++ b/firmware_handler.cpp
@@ -81,10 +81,42 @@
/*
* Per the design, this mean abort, and this will trigger whatever
* appropriate actions are required to abort the process.
+ *
+ * You cannot delete a blob that has an open handle in the system, therefore
+ * this is never called if there's an open session. Guaranteed by the blob
+ * manager.
*/
bool FirmwareBlobHandler::deleteBlob(const std::string& path)
{
- return false;
+ const std::string* toDelete;
+
+ if (path == hashBlobID || path == activeHashBlobID)
+ {
+ /* They're deleting the hash. */
+ toDelete = &activeHashBlobID;
+ }
+ else
+ {
+ /* They're deleting the image. */
+ toDelete = &activeImageBlobID;
+ }
+
+ auto it = std::find_if(
+ blobIDs.begin(), blobIDs.end(),
+ [toDelete](const auto& iter) { return (iter == *toDelete); });
+ if (it == blobIDs.end())
+ {
+ /* Somehow they've asked to delete something we didn't say we could
+ * handle.
+ */
+ return false;
+ }
+
+ blobIDs.erase(it);
+
+ /* TODO: Handle aborting the process and fixing up the state. */
+
+ return true;
}
/*