Not being able to lock down Open Cloud DataStore operations to certain OrderedDataStores by name (like how you can with GlobalDataStore operations) is a big security vulnerability. I can’t justify to my employer the use of Open Cloud’s OrderedDataStore operations in our external services because of this design flaw in Open Cloud’s implementation of OrderedDataStore operations. The options in question:
GlobalDataStores:
OrderedDataStores:
The ability to lock down Open Cloud OrderedDataStore operations to a DataStore by name is very important. I’m confused as to why it was included in the GlobalDataStore option, but not the OrderedDataStore option.