{"action":"created","issue":{"url":"https://api.github.com/repos/elastic/curator/issues/393","labels_url":"https://api.github.com/repos/elastic/curator/issues/393/labels{/name}","comments_url":"https://api.github.com/repos/elastic/curator/issues/393/comments","events_url":"https://api.github.com/repos/elastic/curator/issues/393/events","html_url":"https://github.com/elastic/curator/issues/393","id":86334569,"number":393,"title":"Support latest snapshot restoration","user":{"login":"pickypg","id":1501235,"avatar_url":"https://avatars.githubusercontent.com/u/1501235?v=3","gravatar_id":"","url":"https://api.github.com/users/pickypg","html_url":"https://github.com/pickypg","followers_url":"https://api.github.com/users/pickypg/followers","following_url":"https://api.github.com/users/pickypg/following{/other_user}","gists_url":"https://api.github.com/users/pickypg/gists{/gist_id}","starred_url":"https://api.github.com/users/pickypg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pickypg/subscriptions","organizations_url":"https://api.github.com/users/pickypg/orgs","repos_url":"https://api.github.com/users/pickypg/repos","events_url":"https://api.github.com/users/pickypg/events{/privacy}","received_events_url":"https://api.github.com/users/pickypg/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-06-08T21:18:47Z","updated_at":"2015-07-06T21:14:29Z","closed_at":null,"body":"The support for snapshotting is phenomenal to the point where it's incredibly easy to automate.  It would be great if we could take advantage of this on a secondary cluster to perform automatic restoration. Something along the lines of:\r\n\r\n```shell\r\n$ curator restore --repository REPO_NAME snapshot --latest-snapshot\r\n```\r\n\r\nUnder the hood, this should be able to simply grab the existing snapshots from that repository and find the newest one. The nicest part is that, as long as you end up with a single snapshot at the end, the `--latest-snapshot` option on the `snapshot` subcommand could simply be an augmentation rather than a requirement (e.g., it gives the latest of all returned options, so you could combine it with the other options, even including `--newer-than` and `--older-than`)."},"comment":{"url":"https://api.github.com/repos/elastic/curator/issues/comments/119000210","html_url":"https://github.com/elastic/curator/issues/393#issuecomment-119000210","issue_url":"https://api.github.com/repos/elastic/curator/issues/393","id":119000210,"user":{"login":"untergeek","id":1020383,"avatar_url":"https://avatars.githubusercontent.com/u/1020383?v=3","gravatar_id":"","url":"https://api.github.com/users/untergeek","html_url":"https://github.com/untergeek","followers_url":"https://api.github.com/users/untergeek/followers","following_url":"https://api.github.com/users/untergeek/following{/other_user}","gists_url":"https://api.github.com/users/untergeek/gists{/gist_id}","starred_url":"https://api.github.com/users/untergeek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/untergeek/subscriptions","organizations_url":"https://api.github.com/users/untergeek/orgs","repos_url":"https://api.github.com/users/untergeek/repos","events_url":"https://api.github.com/users/untergeek/events{/privacy}","received_events_url":"https://api.github.com/users/untergeek/received_events","type":"User","site_admin":false},"created_at":"2015-07-06T21:14:29Z","updated_at":"2015-07-06T21:14:29Z","body":"I haven't taken the time to add it because restore is a much less common use-case (or at least, it was) than backup is.  I have an issue now requesting it, so it's on my plate now :smile: "}}