Auto-creation of collections should be configurable #139
Labels
admin-console
Issues related to the Admin Console
breaking
The resolution creates a breaking API change
enhancement
New feature or request
server
Issues related to the server
Milestone
Versions
Description
At the moment, if you create a model in a collection that does not exist, the collection is auto created. It would be good if this behavior could be disabled to allow models to only be created in existing collections. This would prevent accidentally creating a model in the wrong collection due to a typo or programming error.
This would be a per-domain configuration and need to be added to the settings for the domain.
An important note here is that this is the only way to effectively control model creation in the system. With the current behavior there is nothing stopping any user in the system from creating a model in a collection that doesn't exist. For existing collection, administrators can control who can create models in which collections. But non-existent collections would be created automatically with generous world permissions allowing anyone to create a model in a new collection.
Breaking Change
This is a somewhat breaking change. If upgrading your server this feature will be enabled by default on existing domains. Additionally, the default domain automatically created will have the feature enabled. So from that perspective it is not breaking. However, any newly created domains will have this feature disabled, which represents a behavior change in the system.
The text was updated successfully, but these errors were encountered: