)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":14985,"name":"Alex Schultz","email":"aschultz@next-development.com","username":"mwhahaha"},"change_message_id":"1981db8e44c7496ffddc56d00d407f64513ded77","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Include keystone::policy class into init.pp manifest."},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Without inclusion of keystone::policy class it is impossible to"},{"line_number":10,"context_line":"deploy customized keystone policies using policy.pp manifest."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Change-Id: Ib5622547a1b720dc5aa8afc140903c86ffe0339d"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"1f013ff3_4ea85f1e","line":9,"updated":"2017-05-15 16:39:36.000000000","message":"It\u0027s not impossible because you can just include keystone::policy in your manifests.  I\u0027m not against the inclusion in init, but this messaging makes it seem like something\u0027s broken. It\u0027s not as it is up to the operator to include both ::keystone and ::keystone::policy","commit_id":"1c79253659c9c444d6e0e734f2738ebcf83da1e9"}]}