)]}'
{"doc/source/user/concepts.rst":[{"author":{"_account_id":1,"name":"James E. Blair","email":"jim@acmegating.com","username":"corvus"},"change_message_id":"837df038b5d1f31d474b9cc9d534a3b16c1b3d2c","unresolved":false,"context_lines":[{"line_number":86,"context_line":"possible to use the same Ansible playbooks in testing and production."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"Ansible and Python 3"},{"line_number":89,"context_line":"--------------------"},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"As noted above, the executor runs Ansible playbooks against the remote"},{"line_number":92,"context_line":"node(s) allocated for the job.  The ``ansible_python_interpreter``"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3fa7e38b_032d8194","line":89,"updated":"2019-09-18 14:28:16.000000000","message":"I don\u0027t think this is the best place for this documentation.  This file is all about introducing basic concepts of Zuul.  It\u0027s for people who have never used Zuul before, and we need to tell them what gating is, and that Zuul uses something called Ansible to run jobs.  The section added is more configuration reference than introductory material.\n\nMy preference would actually be to omit this in Zuul docs and only document it in Nodepool.  Once all supported versions use \"auto\", that will make a lot of sense.  But now we are in a weird situation where there is still some logic dealing with this in Zuul, so it would be weird not to describe that in Zuul\u0027s docs somewhere.  So if we want to keep this in Zuul\u0027s docs too, then I\u0027d suggest putting it after this section:\n\nhttps://zuul-ci.org/docs/zuul/admin/components.html#executor","commit_id":"39f667dd4afb40503d6f2f69c1df67b8399b2969"}]}