)]}'
{"roles/zuul-ensure-gearman-tls/tasks/main.yaml":[{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"eae852d45cf428e39894b159c7db00b98789b155","unresolved":false,"context_lines":[{"line_number":41,"context_line":"  loop:"},{"line_number":42,"context_line":"    - ca.pem"},{"line_number":43,"context_line":"    - client.key"},{"line_number":44,"context_line":"    - client.pem"}],"source_content_type":"text/x-yaml","patch_set":7,"id":"3fa7e38b_89874b5c","line":44,"updated":"2020-02-03 17:34:53.000000000","message":"Couple things. This task won\u0027t run on the first pass through here. Should we add another set fact on line 35 to allow a single pass to cover all steps?\n\nAlso the files written by \u0027Generate certs\u0027 have different names than the files written by this local write task. Should we have a follow on task rm the server-.* and client-.* files that were generated? It isn\u0027t clear to me which filesystem context this set of tasks runs in.","commit_id":"979b4ce502d47473a3e11efa9bb4d0751407e802"},{"author":{"_account_id":9311,"name":"Tristan Cacqueray","email":"tdecacqu@redhat.com","username":"tristanC"},"change_message_id":"05c85e0c9a7773b62837faedfcfab1c147e85384","unresolved":false,"context_lines":[{"line_number":41,"context_line":"  loop:"},{"line_number":42,"context_line":"    - ca.pem"},{"line_number":43,"context_line":"    - client.key"},{"line_number":44,"context_line":"    - client.pem"}],"source_content_type":"text/x-yaml","patch_set":7,"id":"3fa7e38b_0944bb72","line":44,"in_reply_to":"3fa7e38b_89874b5c","updated":"2020-02-03 18:06:54.000000000","message":"That\u0027s a good point, and the file name could match. Though those files are not meant to be used on the first pass, i should have documented that\u0027s meant to access the gearman service to restart the scheduler, which can only happen on further execution if the zuul.conf change.","commit_id":"979b4ce502d47473a3e11efa9bb4d0751407e802"}]}