)]}'
{"guidelines/tags.rst":[{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"0a3e69cfb2fa0245f9f215177e69bad74b2d22c0","unresolved":false,"context_lines":[{"line_number":125,"context_line":"~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":126,"context_line":""},{"line_number":127,"context_line":"When creating a resource that has tags, include the tags as you would any other"},{"line_number":128,"context_line":"attribute for that resource."},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"Example request for creating a server with tags::"},{"line_number":131,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_9d3c21c0","line":128,"updated":"2019-03-12 08:30:38.000000000","message":"Thanks for this. I failed to find time to write it down (as the ML thread owner).","commit_id":"5678c45ae9743402950b95d503d006e2b154106c"},{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"0a3e69cfb2fa0245f9f215177e69bad74b2d22c0","unresolved":false,"context_lines":[{"line_number":137,"context_line":"        ..."},{"line_number":138,"context_line":"    }"},{"line_number":139,"context_line":""},{"line_number":140,"context_line":"To add, remove, or change tags for an existing resource, a PUT request should"},{"line_number":141,"context_line":"be sent to the root tags URL, with the updated complete list of tags in the"},{"line_number":142,"context_line":"body of the request. On success, the server responds with a 200 status code and"},{"line_number":143,"context_line":"the complete updated tag list in the response body."},{"line_number":144,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_40bb290d","line":141,"range":{"start_line":140,"start_character":57,"end_line":141,"end_character":29},"updated":"2019-03-12 08:30:38.000000000","message":"(Side discussion)\n\nis there any reason we don\u0027t support to update tags in the same way as for in resource creation?\n\n PUT /resources/{id}\n    {\n        \"tags\": [\"foo\", \"bar\"],\n    }\n\nThis is what we usually use when updating/patching an attribute.\n\nCurrently we suggest to use the root tags URL when updating tags. It make OpenStackSDK and OSC implementations a bit tricky. When updating a resource, we need to call two PUT APIs \n(the one for updating usual attributes and the other for updating tags).\n\nI don\u0027t oppose the current way, but it would be nice if we also support to update tags via resource attribute (as we document for creating a resource in this commit).\n\nThought?","commit_id":"5678c45ae9743402950b95d503d006e2b154106c"},{"author":{"_account_id":1063,"name":"Ed Leafe","email":"ed@leafe.com","username":"ed-leafe"},"change_message_id":"ca20181b0c1126590184f1e1e0058d08a29f5043","unresolved":false,"context_lines":[{"line_number":137,"context_line":"        ..."},{"line_number":138,"context_line":"    }"},{"line_number":139,"context_line":""},{"line_number":140,"context_line":"To add, remove, or change tags for an existing resource, a PUT request should"},{"line_number":141,"context_line":"be sent to the root tags URL, with the updated complete list of tags in the"},{"line_number":142,"context_line":"body of the request. On success, the server responds with a 200 status code and"},{"line_number":143,"context_line":"the complete updated tag list in the response body."},{"line_number":144,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_46c33339","line":141,"range":{"start_line":140,"start_character":57,"end_line":141,"end_character":29},"in_reply_to":"5fc1f717_40bb290d","updated":"2019-03-12 14:53:50.000000000","message":"That\u0027s a very good point. Since they are returned along with other resource attributes, they should be able to be set the same way.\n\nI\u0027ll add that to the agenda for the next API-SIG meeting","commit_id":"5678c45ae9743402950b95d503d006e2b154106c"},{"author":{"_account_id":10670,"name":"Michael McCune","email":"elmiko@redhat.com","username":"mimccune"},"change_message_id":"eea7924b82b46ae5833655e4ab1082a67160a324","unresolved":false,"context_lines":[{"line_number":137,"context_line":"        ..."},{"line_number":138,"context_line":"    }"},{"line_number":139,"context_line":""},{"line_number":140,"context_line":"To add, remove, or change tags for an existing resource, a PUT request should"},{"line_number":141,"context_line":"be sent to the root tags URL, with the updated complete list of tags in the"},{"line_number":142,"context_line":"body of the request. On success, the server responds with a 200 status code and"},{"line_number":143,"context_line":"the complete updated tag list in the response body."},{"line_number":144,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_dd749c38","line":141,"range":{"start_line":140,"start_character":57,"end_line":141,"end_character":29},"in_reply_to":"5fc1f717_46c33339","updated":"2019-04-18 16:08:20.000000000","message":"this seems reasonable to me. unless tags are implemented as a separate resource, being able to update them during the normal course of resource updates sounds like something we should have in the guidance as well.","commit_id":"5678c45ae9743402950b95d503d006e2b154106c"}]}