Justin Nauman 2457d8f116 Removing instead of deprecating Namespace attr ...

- Per discussion, there is no reason to deal
with the complexity of backwards compatibility
with the Namespace attribute on the Restore
domain.

- Also noticed there was an error on the
validation of the BackupController where
the message would actually just be the index
of the error and not the contents of the message
itself.

Signed-off-by: Justin Nauman <justin.r.nauman@gmail.com>

2017-09-05 17:18:10 -05:00

..

backup_controller_test.go

make --snapshot-volumes, --restore-volumes optional with sensible default behavior based on PVProvider existence

2017-08-23 09:47:52 -07:00

backup_controller.go

Removing instead of deprecating Namespace attr

2017-09-05 17:18:10 -05:00

backup_sync_controller_test.go

Initial commit

2017-08-02 13:27:17 -04:00

backup_sync_controller.go

Initial commit

2017-08-02 13:27:17 -04:00

gc_controller_test.go

make PVProvider optional in server config; disallow snap/restore PVs when not provided

2017-08-23 09:46:15 -07:00

gc_controller.go

make PVProvider optional in server config; disallow snap/restore PVs when not provided

2017-08-23 09:46:15 -07:00

interface.go

Initial commit

2017-08-02 13:27:17 -04:00

restore_controller_test.go

Removing instead of deprecating Namespace attr

2017-09-05 17:18:10 -05:00

restore_controller.go

Removing instead of deprecating Namespace attr

2017-09-05 17:18:10 -05:00

schedule_controller_test.go

make --snapshot-volumes, --restore-volumes optional with sensible default behavior based on PVProvider existence

2017-08-23 09:47:52 -07:00

schedule_controller.go

Schedules: treat 1st cron field as minutes

2017-08-10 12:44:00 -04:00