)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":1849,"name":"Joe Gordon","email":"joe.gordon0@gmail.com","username":"jogo"},"change_message_id":"14027e008f02978df8227142df58f150944a4acb","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Pull flavor_ref from config for javelin servers"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"The flavor used by Javelin to create servers should not be hard-coded"},{"line_number":10,"context_line":"like the other resources as it is not created and managed by Javelin."},{"line_number":11,"context_line":"Some test environments require booting test servers using specific"},{"line_number":12,"context_line":"flavors. This instead relies on the flavor_ref configured in tempest.conf,"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"7ac7a964_362b9483","line":9,"updated":"2014-08-15 23:00:57.000000000","message":"the flavor is not hard coded it is controlled by the yam file? why is the yaml file not considered configurable?","commit_id":"d0f4167091e108c0b997c5d2d26e218a5f83f3dd"}]}
