> Unless this can cause disruption for other users using public metadef
See my comment on 2016-02-15 for how a user can potentially disrupt other users, upgrades etc.
@Flavio/Travis
Yes, I think having more restrictive default metadef policies is the way to go here. (As far as I understand it it's ok for regular users just to be able to read the metadefs that an admin has defined).
This one would prevent users creating public metadef namespaces:
"add_metadef_namespace":"rule:admin_required"
Hopefully one patch restricting the policies can address the various bugs I put in.
> Unless this can cause disruption for other users using public metadef
See my comment on 2016-02-15 for how a user can potentially disrupt other users, upgrades etc.
@Flavio/Travis
Yes, I think having more restrictive default metadef policies is the way to go here. (As far as I understand it it's ok for regular users just to be able to read the metadefs that an admin has defined).
This one would prevent users creating public metadef namespaces:
"add_metadef_ namespace" :"rule: admin_required"
Hopefully one patch restricting the policies can address the various bugs I put in.