Nolan Brubaker bb7b0a3c33 Invalidate restores based on missing backups ...

When creating a restore based on a backup that doesn't exist, the
restore should be marked as invalid and the error clearly communicated
so the user understands why the restore wasn't made.

Previously, the restore was left as in progress with an error attached.

Since restores are CRDs and must be updated via a controller, there's
currently not a way to give the client immediate errors.

Signed-off-by: Nolan Brubaker <nolan@heptio.com>

2018-01-08 10:10:01 -05:00

..

backup_controller_test.go

Merge pull request #252 from skriss/delete-backup

2018-01-02 14:26:03 -05:00

backup_controller.go

Merge pull request #250 from ncdc/backup-controller-do-as-much-as-possible

2018-01-03 12:10:51 -08:00

backup_sync_controller_test.go

make language and casing consistent across copyrights

2018-01-02 10:51:49 -08:00

backup_sync_controller.go

make language and casing consistent across copyrights

2018-01-02 10:51:49 -08:00

download_request_controller_test.go

make language and casing consistent across copyrights

2018-01-02 10:51:49 -08:00

download_request_controller.go

make language and casing consistent across copyrights

2018-01-02 10:51:49 -08:00

gc_controller_test.go

Merge pull request #252 from skriss/delete-backup

2018-01-02 14:26:03 -05:00

gc_controller.go

Merge pull request #252 from skriss/delete-backup

2018-01-02 14:26:03 -05:00

interface.go

make language and casing consistent across copyrights

2018-01-02 10:51:49 -08:00

restore_controller_test.go

Invalidate restores based on missing backups

2018-01-08 10:10:01 -05:00

restore_controller.go

Invalidate restores based on missing backups

2018-01-08 10:10:01 -05:00

schedule_controller_test.go

make language and casing consistent across copyrights

2018-01-02 10:51:49 -08:00

schedule_controller.go

make language and casing consistent across copyrights

2018-01-02 10:51:49 -08:00