*** alex_xu has joined #openstack-api | 01:15 | |
*** salv-orl_ has joined #openstack-api | 06:58 | |
*** e0ne has joined #openstack-api | 09:04 | |
*** e0ne has quit IRC | 09:10 | |
*** salv-orlando has joined #openstack-api | 09:13 | |
*** salv-orl_ has quit IRC | 09:13 | |
*** salv-orlando has quit IRC | 09:43 | |
*** salv-orl_ has joined #openstack-api | 09:46 | |
*** salv-orlando has joined #openstack-api | 09:50 | |
*** salv-orl_ has quit IRC | 09:53 | |
*** salv-orl_ has joined #openstack-api | 10:31 | |
*** e0ne has joined #openstack-api | 10:31 | |
*** salv-orlando has quit IRC | 10:34 | |
*** salv-orl_ has quit IRC | 10:46 | |
*** salv-orlando has joined #openstack-api | 10:47 | |
*** salv-orlando has quit IRC | 11:23 | |
*** ryansb has joined #openstack-api | 11:47 | |
*** salv-orlando has joined #openstack-api | 12:24 | |
*** subscope has joined #openstack-api | 12:35 | |
*** salv-orlando has quit IRC | 12:37 | |
*** _elmiko is now known as elmiko | 13:07 | |
*** elmiko has joined #openstack-api | 13:08 | |
*** e0ne has quit IRC | 14:14 | |
*** sigmavirus24_awa is now known as sigmavirus24 | 14:14 | |
*** salv-orlando has joined #openstack-api | 14:16 | |
*** fzdarsky has joined #openstack-api | 14:22 | |
*** salv-orlando has quit IRC | 14:32 | |
*** etoews has quit IRC | 15:19 | |
*** e0ne has joined #openstack-api | 15:28 | |
*** salv-orlando has joined #openstack-api | 15:41 | |
*** sigmavirus24 is now known as Apsu_ | 15:53 | |
*** Apsu_ is now known as sigmavirus24 | 15:53 | |
*** salv-orlando has quit IRC | 16:12 | |
*** fzdarsky has quit IRC | 16:19 | |
*** fzdarsky has joined #openstack-api | 16:22 | |
*** salv-orlando has joined #openstack-api | 17:30 | |
*** salv-orlando has quit IRC | 17:39 | |
*** subscope_ has joined #openstack-api | 18:49 | |
*** salv-orlando has joined #openstack-api | 19:22 | |
*** e0ne has quit IRC | 19:26 | |
*** e0ne has joined #openstack-api | 19:30 | |
*** salv-orlando has quit IRC | 19:33 | |
*** e0ne has quit IRC | 19:35 | |
*** e0ne has joined #openstack-api | 19:37 | |
*** e0ne has quit IRC | 19:39 | |
*** e0ne has joined #openstack-api | 19:39 | |
*** e0ne has quit IRC | 19:41 | |
*** e0ne has joined #openstack-api | 19:42 | |
*** e0ne has quit IRC | 19:42 | |
*** e0ne has joined #openstack-api | 19:43 | |
*** e0ne has quit IRC | 19:43 | |
*** e0ne has joined #openstack-api | 19:45 | |
*** e0ne has quit IRC | 19:45 | |
*** e0ne has joined #openstack-api | 19:57 | |
*** subscope_ has quit IRC | 20:08 | |
*** sigmavirus24 has quit IRC | 20:23 | |
*** sigmavirus24 has joined #openstack-api | 20:24 | |
*** e0ne has quit IRC | 20:26 | |
*** e0ne has joined #openstack-api | 20:30 | |
*** sigmavirus24 has quit IRC | 20:34 | |
*** sigmavirus24 has joined #openstack-api | 20:38 | |
*** joesavak has joined #openstack-api | 20:43 | |
*** e0ne has quit IRC | 20:45 | |
*** etoews has joined #openstack-api | 20:47 | |
*** salv-orlando has joined #openstack-api | 20:55 | |
*** woodster_ has joined #openstack-api | 21:11 | |
woodster_ | Hello folks, I was wondering if guidance on POST vs PUT requests for canonical OpenStack APIs is in the works, per this section?: https://github.com/openstack/api-wg/blob/4319ae3459f1dd79f5fc212c8a8dc38ec4fcd4f1/guidelines/http.rst#http-methods | 21:15 |
---|---|---|
ryansb | woodster_: well, it's a TODO, but I don't think anybody's put a spec up yet | 21:23 |
woodster_ | ryansb: thanks. Yeah we were having a discussion about POST vs PUT on barbican earlier and someone suggested asking the api-wg channel about it. | 21:24 |
woodster_ | ryansb: I was going to look at what other projects were doing in this regard. | 21:25 |
ryansb | ah, well the general guideline (from the RFCs) is to use POST for creates only | 21:25 |
ryansb | and puts for updates | 21:25 |
woodster_ | ryansb: that's been my understanding as well, but someone mentioned that Keystone updates user info via a POST per this example: http://docs.openstack.org/developer/keystone/api_curl_examples.html#post-v3-users-user-id-password | 21:29 |
elmiko | imo, woodster_ you had it correct to being with ;) | 21:32 |
elmiko | *begin | 21:32 |
woodster_ | elmiko: yeah, I was hoping so, but I'm not 100% I'm sure 100% of the time! | 21:34 |
elmiko | hehe, yea. always good to check around =) | 21:34 |
woodster_ | would it be good to bring this up as an agenda item for the next wg meeting time permitting? | 21:36 |
elmiko | yea, definitely | 21:39 |
elmiko | next meeting is this thursday at noon eastern time | 21:39 |
woodster_ | sounds good! Thanks | 21:40 |
elmiko | woodster_: if you don't make it, i'll try to remember to bring it up | 21:40 |
woodster_ | elmiko: that sounds good. | 21:40 |
ryansb | woodster_: also, you can add "APIImpact" in the commit message for specs and reviews | 21:51 |
elmiko | oh yea, good point ryansb | 21:51 |
woodster_ | ryansb: I was thinking such tags were more for a filter target rather than triggering interested parties to review things...is that not the case though? | 21:52 |
*** fzdarsky has quit IRC | 21:53 | |
elmiko | woodster_: in past meetings we have used the APIImpact flag to help direct traffic towards reviews. sometimes we discuss them in the meeting, other times we have just looked at the list to call attention to certain reviews. | 21:58 |
elmiko | it kinda depends on how busy the agenda is, and what topics folks would like to discuss | 21:58 |
ryansb | well we use filters to find them, of course | 22:01 |
ryansb | but I have a query for APIImpact in my gerrit dash, and I try to review new ones in a timely fashion | 22:02 |
elmiko | that's pretty good, i don't even seem to have time left for *Impact reviews =( | 22:04 |
elmiko | *ever | 22:04 |
ryansb | elmiko: I admit to stretching the definition of "timely" a tad | 22:06 |
elmiko | hehe ;) | 22:06 |
elmiko | ryansb: have you met much resistance when making comments about APIImpact? | 22:07 |
ryansb | no, folks are pretty receptive | 22:07 |
elmiko | that's cool | 22:07 |
*** elmiko is now known as _elmiko | 22:28 | |
woodster_ | _elmiko: ryansb that's good to know actually, thanks | 22:31 |
*** joesavak has quit IRC | 22:36 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!