)]}'
{"openstack/compute/v2/server.py":[{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"be8f8b4130709a25617aa601951099bce80436a1","unresolved":true,"context_lines":[{"line_number":41,"context_line":"    # There are valid request parameters that are not resource attributes and"},{"line_number":42,"context_line":"    # are not returned as part of the response body, examples: min_count,"},{"line_number":43,"context_line":"    # max_count"},{"line_number":44,"context_line":"    _allow_unknown_attrs_in_body \u003d True"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"    _query_mapping \u003d resource.QueryParameters("},{"line_number":47,"context_line":"        \"auto_disk_config\", \"availability_zone\","}],"source_content_type":"text/x-python","patch_set":3,"id":"23f85c69_990b740a","line":44,"updated":"2021-04-27 08:53:29.000000000","message":"Any reason we couldn\u0027t just define min_count, max_count below? It won\u0027t be present in responses but it\u0027s perfectly valid for requests. (We have no way currently to mark an attribute as response-only or request-only, nor limited to a particular microversion)","commit_id":"716712e4f753239a5f17c60d2718396c245ad7d4"},{"author":{"_account_id":27900,"name":"Artem Goncharov","email":"artem.goncharov@gmail.com","username":"gtema"},"change_message_id":"f3d45f9655c583b031b400a48598c38dd5aaf6e0","unresolved":true,"context_lines":[{"line_number":41,"context_line":"    # There are valid request parameters that are not resource attributes and"},{"line_number":42,"context_line":"    # are not returned as part of the response body, examples: min_count,"},{"line_number":43,"context_line":"    # max_count"},{"line_number":44,"context_line":"    _allow_unknown_attrs_in_body \u003d True"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"    _query_mapping \u003d resource.QueryParameters("},{"line_number":47,"context_line":"        \"auto_disk_config\", \"availability_zone\","}],"source_content_type":"text/x-python","patch_set":3,"id":"575fccb2_49af8933","line":44,"in_reply_to":"23f85c69_990b740a","updated":"2021-04-27 08:55:59.000000000","message":"There is absolutely no reason to use this very specific feature.","commit_id":"716712e4f753239a5f17c60d2718396c245ad7d4"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"3d76763322d3848799b8bd364a9c7cf65d779abe","unresolved":true,"context_lines":[{"line_number":41,"context_line":"    # There are valid request parameters that are not resource attributes and"},{"line_number":42,"context_line":"    # are not returned as part of the response body, examples: min_count,"},{"line_number":43,"context_line":"    # max_count"},{"line_number":44,"context_line":"    _allow_unknown_attrs_in_body \u003d True"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"    _query_mapping \u003d resource.QueryParameters("},{"line_number":47,"context_line":"        \"auto_disk_config\", \"availability_zone\","}],"source_content_type":"text/x-python","patch_set":3,"id":"18248b74_e235118b","line":44,"in_reply_to":"575fccb2_49af8933","updated":"2021-04-27 17:19:44.000000000","message":"Thanks both for the guidance! I had actually done as you suggest in PS1 😅 but when I encountered unit test failures around expected response content, I thought I had done something wrong and that class attrs were only meant to represent data coming back in a response as well. I’ll revert this back to PS1 + unit test updates for the expected response contents.","commit_id":"716712e4f753239a5f17c60d2718396c245ad7d4"}]}