crush rule min_size

Hi, The crush rule min_size property is easily confused with pool min_size. One could imagine a data loss scenario where an operator "fixed" a misconfigured cluster by setting the crush rule min_size to 2 (but left a pool min_size at 1). Should we rename one of them (... the crush one)? ... e.g. min_osds/max_osds ? Going further, do we even have a use-case for manually changing a crush_rule's min_size/max_size. Could we simply hide them and hardcode internally to min_size=1 and max_size=100? Cheers, Dan