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

..

apis/ark/v1

Removing instead of deprecating Namespace attr

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

backup

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

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

buildinfo

Initial commit

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

client

Pull in azure, gcp, oidc client-go auth provider plugins

2017-08-07 11:24:22 -04:00

cloudprovider

get rid of StorageAdapter structs and move validation into block/object

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

cmd

Additional Validation on Include/Exclude

2017-09-05 17:17:46 -05:00

controller

Removing instead of deprecating Namespace attr

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

discovery

Initial commit

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

generated

Initial commit

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

restore

Allows explicit include/exclude of namespaces on restores

2017-09-05 17:17:41 -05:00

util

Removing instead of deprecating Namespace attr

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