Comment 6 for bug 1525259

Thanks Abhishek for filing the lite-spec for this.

@Stuart, Thanks for digging into this!

I personally prefer this alternative approach the most at the moment. It looks like the "most right way" to do this in our current model. I'm really not fond of original approach 2 as that would give the impression that request_id is a property in our image (so which request id we refer here, the one that created the image, the last one that modified it or something else). If using the hooks provides us access to the req id's without changing our schema and without wrapping the whole warlock object around, that really sounds like the way to go. and the implementation in the client seems fairly clean and easy to understand as well.