Feature #17696
Updated by Ward Vandewege over 2 years ago
Use case: the default storage classes should be configurable in the config file, and there can be more than one.
* api/controller reads Collections/DefaultStorageClasses map[string]bool. The default value will be {"default":true} (aka one storage class named "default").
* when new collections are stored (and no storage classes are requested) the default values should be added to the desired storage classes
* update those clients that send "default" as the storage class to send nothing instead
* need a migration? for existing collections with storage class "default". Add a python recipe to the cookbook to change a particular storage class (e.g. "default") to something else.
* validation on the config check. Make sure the default class(es) are implemented by a volume.
* add some tests