Also of note, there are some methods that show a return of 501 and then other options
greyed out underneath. That is to convey that we currently do not implement this
otherwise in imagefactory, but when we do, the greyed out return possibilities are what
I'm thinking we would do. Those methods that I do not see us implementing in the
future are noted by the 405 return code.
-steve
On Aug 22, 2011, at 1:33 PM, Steve Loranz wrote:
We are looking to add REST as an option to interfacing with
imagefactory in our next sprint. It would be very helpful if people would have a look at
the current proposed definition at
https://www.aeolusproject.org/redmine/issues/2142 and
comment.
For those of you that do review this, I went back and forth on having "import"
be an actionable resource or just overloading the URI by putting import on PUT where as
building is on POST. Please weigh in on which way you would rather see it. I don't
like that it stands out as opposed to building and pushing, but that's maybe a
nitpick.
.pdf
https://www.aeolusproject.org/redmine/attachments/159/imagefactory-REST.pdf
.ods
https://www.aeolusproject.org/redmine/attachments/160/imagefactory-REST.ods
Thank you for your time.
-steve
_______________________________________________
aeolus-devel mailing list
aeolus-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/aeolus-devel