You can not only set experience level permissions, i.e. We understand the importance of your data, and so designed fine granular permission control when creating your API keys, which include datastore entry operations (create, list, update, and read), versioning (read and list), and datastore creation and listing. You can list datastores in an experience as well as listing, reading, and writing entries in a specific datastore. The new Datastore APIs have the same functionality as Lua ones. Data migration script: script that reads from current datastores, changes the schema, and writes to a new datastore.
LiveOps dashboard: A Liveops dashboard can allow you to schedule in-game events such as Halloween parties by updating Datastore in real-time and also monitor the key metrics.Customer support portal: You can build a web application that allows your CS agents/moderators to view and modify player data when handling player support requests.Some of the tools you can potentially build include: The new Datastore API means to unlock your productivity by automating many of your key workflows. Previously, you could only access your production data either from Studio or a live game, which is inconvenient for many use cases such as offering customer support (CS). We started with the Place Publishing API so you can automate the continuous delivery process.īased on the community feedback, we understand that supporting Datastore endpoints will be super valuable. Having a rich set of APIs is at the core of this initiative. The vision for Open Cloud is to empower an application ecosystem where you can either build or find all the tools you need.
After planning, implementing, and testing over the past few months, we are excited to announce the launch of Datastore APIs for Open Cloud!
0 kommentar(er)
