)]}'
{"magnum/drivers/common/templates/kubernetes/fragments/enable-ingress-traefik.sh":[{"author":{"_account_id":20498,"name":"Spyros Trigazis","email":"spyridon.trigazis@cern.ch","username":"strigazi"},"change_message_id":"c4a8e4ecdee276b8b5e733886ee562e9d32f7125","unresolved":false,"context_lines":[{"line_number":175,"context_line":"    sleep 5"},{"line_number":176,"context_line":"done"},{"line_number":177,"context_line":""},{"line_number":178,"context_line":"kubectl apply -f ${INGRESS_TRAEFIK_MANIFEST}"}],"source_content_type":"text/x-sh","patch_set":2,"id":"1f493fa4_11522e14","line":178,"updated":"2020-04-22 14:33:28.000000000","message":"this works [0] too, but we don\u0027t do it anywhere else.\n\n[0]\n # Check if all resources exist already before creating them\n if [ ! kubectl -n kube-system get service ingress-traefik ] \n ; then\n     kubectl apply -f ${INGRESS_TRAEFIK_MANIFEST}\n fi","commit_id":"3e7924ffda45a1d750700ff1e86019359f90870c"},{"author":{"_account_id":6484,"name":"Feilong Wang","email":"hustemb@gmail.com","username":"flwang"},"change_message_id":"fcdfa589b0f783b502a28b5cc9b78855ae7c9894","unresolved":false,"context_lines":[{"line_number":175,"context_line":"    sleep 5"},{"line_number":176,"context_line":"done"},{"line_number":177,"context_line":""},{"line_number":178,"context_line":"kubectl apply -f ${INGRESS_TRAEFIK_MANIFEST}"}],"source_content_type":"text/x-sh","patch_set":2,"id":"1f493fa4_d06397db","line":178,"in_reply_to":"1f493fa4_11522e14","updated":"2020-04-22 21:22:11.000000000","message":"I kind of like this but it\u0027s not a blocker. And this triggers me a feature that the user can disable an addon for an existing cluster.","commit_id":"3e7924ffda45a1d750700ff1e86019359f90870c"}]}