{"action":"opened","issue":{"url":"https://api.github.com/repos/argoproj/argo-cd/issues/818","repository_url":"https://api.github.com/repos/argoproj/argo-cd","labels_url":"https://api.github.com/repos/argoproj/argo-cd/issues/818/labels{/name}","comments_url":"https://api.github.com/repos/argoproj/argo-cd/issues/818/comments","events_url":"https://api.github.com/repos/argoproj/argo-cd/issues/818/events","html_url":"https://github.com/argoproj/argo-cd/issues/818","id":382675456,"node_id":"MDU6SXNzdWUzODI2NzU0NTY=","number":818,"title":"Resolve ambiguous revision to commitSHA at sync time","user":{"login":"jessesuen","id":12677113,"node_id":"MDQ6VXNlcjEyNjc3MTEz","avatar_url":"https://avatars0.githubusercontent.com/u/12677113?v=4","gravatar_id":"","url":"https://api.github.com/users/jessesuen","html_url":"https://github.com/jessesuen","followers_url":"https://api.github.com/users/jessesuen/followers","following_url":"https://api.github.com/users/jessesuen/following{/other_user}","gists_url":"https://api.github.com/users/jessesuen/gists{/gist_id}","starred_url":"https://api.github.com/users/jessesuen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jessesuen/subscriptions","organizations_url":"https://api.github.com/users/jessesuen/orgs","repos_url":"https://api.github.com/users/jessesuen/repos","events_url":"https://api.github.com/users/jessesuen/events{/privacy}","received_events_url":"https://api.github.com/users/jessesuen/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-11-20T13:58:42Z","updated_at":"2018-11-20T13:58:42Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"We will have better event logging/audit trails if we resolve the ambiguous git revision at the API server at the time of sync (which is when the event is emitted). This way instead of:\r\n\r\n> user admin initiated sync to HEAD\r\nit would be\r\n> user admin initiated sync to HEAD (abc1234)\r\n\r\nIt also means that theres zero chance a second commit can jump in between the time the sync was requested, and when the controller picked it up to resolve the revision."}}
{"actor":{"display_login":"jessesuen"}}