)]}'
{"playbooks/roles/gitea/tasks/main.yaml":[{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"11b1abfe10335c7c1ffedda4cdef7af81f08e656","unresolved":false,"context_lines":[{"line_number":38,"context_line":"# Create the services so they can be stopped on first pass"},{"line_number":39,"context_line":"- name: Run docker-compose up --no-start"},{"line_number":40,"context_line":"  shell:"},{"line_number":41,"context_line":"    cmd: docker-compose up --no-start"},{"line_number":42,"context_line":"    chdir: /etc/gitea-docker/"},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"- name: Stop/Start gitea safely for Gerrit replication"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"1fa4df85_f6b778d7","line":41,"updated":"2020-03-18 20:18:25.000000000","message":"We should test that this doesn\u0027t have ill effects on a running set of services. I believe it is necessary to bootstrap the services on first run, but not sure what kind of side effects it would have on running services.\n\nAlso its possible the pull above implies a no-start creation type step? I suppose I can push a followup change that remove this and tests it.","commit_id":"5be70cc7b0649cdfc8f3f224bf2b4c9b4dcc2db8"},{"author":{"_account_id":2,"name":"Monty Taylor","email":"mordred@inaugust.com","username":"mordred"},"change_message_id":"d7499abe0ac9b69a96465cff68d5237278d4057f","unresolved":false,"context_lines":[{"line_number":38,"context_line":"# Create the services so they can be stopped on first pass"},{"line_number":39,"context_line":"- name: Run docker-compose up --no-start"},{"line_number":40,"context_line":"  shell:"},{"line_number":41,"context_line":"    cmd: docker-compose up --no-start"},{"line_number":42,"context_line":"    chdir: /etc/gitea-docker/"},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"- name: Stop/Start gitea safely for Gerrit replication"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"1fa4df85_2dc93e77","line":41,"in_reply_to":"1fa4df85_f6b778d7","updated":"2020-03-18 22:09:07.000000000","message":"Turns out this isn\u0027t needed.","commit_id":"5be70cc7b0649cdfc8f3f224bf2b4c9b4dcc2db8"},{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"11b1abfe10335c7c1ffedda4cdef7af81f08e656","unresolved":false,"context_lines":[{"line_number":42,"context_line":"    chdir: /etc/gitea-docker/"},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"- name: Stop/Start gitea safely for Gerrit replication"},{"line_number":45,"context_line":"  when: \"\u0027Downloaded newer image\u0027 in docker_compose_pull.stdout\""},{"line_number":46,"context_line":"  block:"},{"line_number":47,"context_line":"    - name: Run docker-compose stop"},{"line_number":48,"context_line":"      shell:"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"1fa4df85_b6b100e4","line":45,"updated":"2020-03-18 20:18:25.000000000","message":"I actually took this from `docker pull`s output but it seems to be the same with docker compose.","commit_id":"5be70cc7b0649cdfc8f3f224bf2b4c9b4dcc2db8"},{"author":{"_account_id":2,"name":"Monty Taylor","email":"mordred@inaugust.com","username":"mordred"},"change_message_id":"27b7ca44611da6a1939881ebc0c565106decf24d","unresolved":false,"context_lines":[{"line_number":101,"context_line":"          send_notify: false"},{"line_number":102,"context_line":"          source_id: 0"},{"line_number":103,"context_line":"          username: gerrit"},{"line_number":104,"context_line":"    - name: Check if gerrit ssh key exists"},{"line_number":105,"context_line":"      uri:"},{"line_number":106,"context_line":"        user: root"},{"line_number":107,"context_line":"        password: \"{{ gitea_root_password }}\""}],"source_content_type":"text/x-yaml","patch_set":4,"id":"1fa4df85_eddc8619","line":104,"updated":"2020-03-18 22:19:50.000000000","message":"Starting here we might not want to only do this on new images - since there is logic below to update a key.","commit_id":"e1b58d97abc31b2e4241b287efe3d9f20828783e"},{"author":{"_account_id":1,"name":"James E. Blair","email":"jim@acmegating.com","username":"corvus"},"change_message_id":"be362c7be7dae5ecbe7c0f9506e8bf4e652c816a","unresolved":false,"context_lines":[{"line_number":67,"context_line":"    - name: Run docker prune to cleanup unneeded images"},{"line_number":68,"context_line":"      shell:"},{"line_number":69,"context_line":"        cmd: docker image prune -f"},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"    - name: Create root user"},{"line_number":72,"context_line":"      when: root_user_check.status\u003d\u003d404"},{"line_number":73,"context_line":"      block:"}],"source_content_type":"text/x-yaml","patch_set":5,"id":"1fa4df85_cdbaea6c","line":70,"updated":"2020-03-18 22:46:40.000000000","message":"How about we exit the block here (and re-run the root check), since the rest doesn\u0027t strictly relate to a new image?","commit_id":"9240980b6123f1eb266655b52dfc9838d0359be8"}]}