)]}'
{"lib/puppet/type/glance_image.rb":[{"author":{"_account_id":7745,"name":"Denis Egorenko","email":"degorenko@mirantis.com","username":"degorenko"},"change_message_id":"7d2d7e1489549c87e43a89ed86f774e76d2e9de3","unresolved":false,"context_lines":[{"line_number":98,"context_line":"      rv \u003d endpoints.map do |e|"},{"line_number":99,"context_line":"        e.name"},{"line_number":100,"context_line":"      end"},{"line_number":101,"context_line":"    end"},{"line_number":102,"context_line":"    rv"},{"line_number":103,"context_line":"  end"},{"line_number":104,"context_line":"end"}],"source_content_type":"text/x-ruby","patch_set":1,"id":"ba0121b8_7dd66fc6","line":101,"updated":"2016-03-29 08:59:47.000000000","message":"it will not help, when we have some order of applying manifests, based on different runs and different catalogs.\n\nso, for example, fuel uses task-base deployment. That means, that we have separate tasks for creating endpoint and for deploying glance at all. Hence we have different catalogs.\n\nWhy not just use collectors for finding endpoint? It will help in one catalog and will not fail in different.","commit_id":"dc299a82a951d044676fcfee9f5e0972e7e2c82f"}]}