{"action":"closed","issue":{"url":"https://api.github.com/repos/ArthurHlt/test-mirroring/issues/8","repository_url":"https://api.github.com/repos/ArthurHlt/test-mirroring","labels_url":"https://api.github.com/repos/ArthurHlt/test-mirroring/issues/8/labels{/name}","comments_url":"https://api.github.com/repos/ArthurHlt/test-mirroring/issues/8/comments","events_url":"https://api.github.com/repos/ArthurHlt/test-mirroring/issues/8/events","html_url":"https://github.com/ArthurHlt/test-mirroring/issues/8","id":165848164,"number":8,"title":"CLI plugin restore UX: avoid data loss from incorrect argument passing - unscheduled - Story Id: 126232405","user":{"login":"ArthurHlt","id":5410858,"avatar_url":"https://avatars.githubusercontent.com/u/5410858?v=3","gravatar_id":"","url":"https://api.github.com/users/ArthurHlt","html_url":"https://github.com/ArthurHlt","followers_url":"https://api.github.com/users/ArthurHlt/followers","following_url":"https://api.github.com/users/ArthurHlt/following{/other_user}","gists_url":"https://api.github.com/users/ArthurHlt/gists{/gist_id}","starred_url":"https://api.github.com/users/ArthurHlt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ArthurHlt/subscriptions","organizations_url":"https://api.github.com/users/ArthurHlt/orgs","repos_url":"https://api.github.com/users/ArthurHlt/repos","events_url":"https://api.github.com/users/ArthurHlt/events{/privacy}","received_events_url":"https://api.github.com/users/ArthurHlt/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/ArthurHlt/test-mirroring/labels/feature","name":"feature","color":"ededed"}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-07-15T18:20:30Z","updated_at":"2016-07-28T12:05:14Z","closed_at":"2016-07-28T12:05:14Z","body":"- **Link**: https://www.pivotaltracker.com/story/show/126232405\n- **Labels**: \n- **Requester**: Guillaume Berche\n- **Estimate**: 0.0\n\nRestoring a dump into a db is a destructive operation. Ambiguity in the command might lead to data loss\n\ncurrent UX is error prone: \n* confusion betwen db and dumps service instance\n* lack distinction between source and target\n* lack recap of operation that will be applied and operation confirmation of the destructive operation\n\n```\ncf db-dumper help r\nNAME:\n   db-dumper_linux_amd64 restore - Restore a dump from a database service or database uri (e.g: mysql://admin:admin@mybase.com:3306/mysuperdb)\n\nUSAGE:\n   db-dumper_linux_amd64 restore [command options] [service-name-or-url-of-your-db]\n\nOPTIONS:\n   --recent                 Restore from the most recent dump\n   --source-instance value  The db dumper service instance where dumps should be retrieved (this can be the service instance you passed in create e.g.: mydb)\n  \n\n\n$ cf s\nGetting services in org orange / space gberche as gberche...\nOK\n\nname                               service             plan        bound apps                          last operation\nmysql-spring-travel                p-mysql             100mb       phpmyadmin-cfready, spring-travel   create succeeded\na3dee8f9mysql-spring-travel-dump   db-dumper-service   unlimited                                       update succeeded\nmysql-spring-travel-copy           p-mysql             100mb                                           create succeeded\nguillaume@guillaume-box:~/code/workspaceElPaasov14/phpmyadmin-cf/cf-ready/phpmyadmin-cf-cf-ready$ cf db-dumper r a3dee8f9mysql-spring-travel-dump\nSearching available db-dumper-service instances...\n\nAvailable db-dumper-service instances\n0. mysql-spring-travel\n\nWhich instance do you want to restore to 'a3dee8f9mysql-spring-travel-dump' ?\n```\n\n```\n$ cf db-dumper r mysql-spring-travel-copy --source-instance a3dee8f9mysql-spring-travel-dump\nAvailable dump dates:\n0. 13-07-2016 15:17\n1. 13-07-2016 11:48\n\nAt which date do you want to restore ?\nChoice <recent>: 0\nRestoring dump finished.\n```\n\n"}}
{"actor":{"display_login":"ArthurHlt"}}