{"action":"opened","issue":{"url":"https://api.github.com/repos/Azure/azure-sdk-for-go/issues/424","repository_url":"https://api.github.com/repos/Azure/azure-sdk-for-go","labels_url":"https://api.github.com/repos/Azure/azure-sdk-for-go/issues/424/labels{/name}","comments_url":"https://api.github.com/repos/Azure/azure-sdk-for-go/issues/424/comments","events_url":"https://api.github.com/repos/Azure/azure-sdk-for-go/issues/424/events","html_url":"https://github.com/Azure/azure-sdk-for-go/issues/424","id":185055837,"number":424,"title":"Abort Copy Blob operation.","user":{"login":"kpfaulkner","id":116306,"avatar_url":"https://avatars.githubusercontent.com/u/116306?v=3","gravatar_id":"","url":"https://api.github.com/users/kpfaulkner","html_url":"https://github.com/kpfaulkner","followers_url":"https://api.github.com/users/kpfaulkner/followers","following_url":"https://api.github.com/users/kpfaulkner/following{/other_user}","gists_url":"https://api.github.com/users/kpfaulkner/gists{/gist_id}","starred_url":"https://api.github.com/users/kpfaulkner/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kpfaulkner/subscriptions","organizations_url":"https://api.github.com/users/kpfaulkner/orgs","repos_url":"https://api.github.com/users/kpfaulkner/repos","events_url":"https://api.github.com/users/kpfaulkner/events{/privacy}","received_events_url":"https://api.github.com/users/kpfaulkner/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-10-25T08:51:49Z","updated_at":"2016-10-25T08:51:49Z","closed_at":null,"body":"Currently the library supports the starting of a copy blob operation (CopyBlob function) which starts a single copy and then waits. \r\n\r\nI'd like to propose a new function for Aborting such a copy (see https://msdn.microsoft.com/en-us/library/azure/jj159098.aspx) as well as modifying the existing code a tiny bit.\r\n\r\nCurrently the exported function CopyBlob calls a non-exported (still trying to get my Go jargon right) startBlobCopy, then once the copying has started it loops checking the status.\r\n\r\nI'd like to propose the following changes:\r\n\r\n- make startBlobCopy exportable (ie name it StartBlobCopy) that way people can easily fire off a bunch of them without having to perform the wait.\r\n- Add AbortBlobCopy which takes the copyID generated by startBlobCopy and can abort the operation if needed.\r\n\r\nNo functionality (CopyBlob function) is impacted but gives the users 2 methods (StartBlobCopy and AbortBlobCopy) which are closer (and for me personally more useful) to the REST API.\r\n\r\nI've already coded up a PR with the above, but wanted to get opinions before I actually submit it.\r\n\r\nThoughts?"}}
{"actor":{"display_login":"kpfaulkner"}}