{"action":"created","issue":{"url":"https://api.github.com/repos/spatie/laravel-backup/issues/188","repository_url":"https://api.github.com/repos/spatie/laravel-backup","labels_url":"https://api.github.com/repos/spatie/laravel-backup/issues/188/labels{/name}","comments_url":"https://api.github.com/repos/spatie/laravel-backup/issues/188/comments","events_url":"https://api.github.com/repos/spatie/laravel-backup/issues/188/events","html_url":"https://github.com/spatie/laravel-backup/issues/188","id":171208055,"number":188,"title":"Write only mode for AWS","user":{"login":"barryvdh","id":973269,"avatar_url":"https://avatars.githubusercontent.com/u/973269?v=3","gravatar_id":"","url":"https://api.github.com/users/barryvdh","html_url":"https://github.com/barryvdh","followers_url":"https://api.github.com/users/barryvdh/followers","following_url":"https://api.github.com/users/barryvdh/following{/other_user}","gists_url":"https://api.github.com/users/barryvdh/gists{/gist_id}","starred_url":"https://api.github.com/users/barryvdh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/barryvdh/subscriptions","organizations_url":"https://api.github.com/users/barryvdh/orgs","repos_url":"https://api.github.com/users/barryvdh/repos","events_url":"https://api.github.com/users/barryvdh/events{/privacy}","received_events_url":"https://api.github.com/users/barryvdh/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-08-15T16:34:28Z","updated_at":"2016-08-15T18:42:01Z","closed_at":null,"body":"Is it possible to use a 'write only' mode, without listing/reading, for Amazon AWS?\r\n\r\nEg. I have a policy that only allows a 'PUT' command, so that a backup service can only ever put new backups and not read/delete them.\r\n\r\nThis combined with the Amazon versioning + lifecycle to move to glacier, makes sure that files are never deleted (unless the period is over). Do you have a recommended way to do this?"},"comment":{"url":"https://api.github.com/repos/spatie/laravel-backup/issues/comments/239889851","html_url":"https://github.com/spatie/laravel-backup/issues/188#issuecomment-239889851","issue_url":"https://api.github.com/repos/spatie/laravel-backup/issues/188","id":239889851,"user":{"login":"barryvdh","id":973269,"avatar_url":"https://avatars.githubusercontent.com/u/973269?v=3","gravatar_id":"","url":"https://api.github.com/users/barryvdh","html_url":"https://github.com/barryvdh","followers_url":"https://api.github.com/users/barryvdh/followers","following_url":"https://api.github.com/users/barryvdh/following{/other_user}","gists_url":"https://api.github.com/users/barryvdh/gists{/gist_id}","starred_url":"https://api.github.com/users/barryvdh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/barryvdh/subscriptions","organizations_url":"https://api.github.com/users/barryvdh/orgs","repos_url":"https://api.github.com/users/barryvdh/repos","events_url":"https://api.github.com/users/barryvdh/events{/privacy}","received_events_url":"https://api.github.com/users/barryvdh/received_events","type":"User","site_admin":false},"created_at":"2016-08-15T18:42:01Z","updated_at":"2016-08-15T18:42:01Z","body":"I got a problem earlier when I tried, should have mentioned that. It tried again and looked further.\r\n\r\nBefore creating a backup, `isReachable()` is called, which lists all files. This is not allowed (in my current policy).\r\nIs that for performance, or a different reason? Looking in the code, it seems that first the Zip is created (the heavy part), and then the destinations are checked and immediately after the stream is written. If a destination is not reachable, the stream operation would fail directly anyway, right? So is the directory listing even necessary?\r\n\r\nSecond thing is that the filename is not configurable, right? That would be needed to use AWS versioning (same filename). This could be fixed by allowing an optional filename flag perhaps?\r\n\r\n```\r\nphp artisan backup:run --only-db --filename=db.zip \r\nphp artisan backup:run --only-files --filename=media.zip \r\n```\r\n\r\nIf you want I can create a PR for both issues."}}
{"actor":{"display_login":"barryvdh"}}