Deployment package
The Deployment package provides a cohesive interface to deploy assets for Unity Gaming Services (UGS). It provides the base tooling for UGS to have shared functionality for deploying service configuration files on the servers.
Note
A deployment is when service configuration files are synced with service resources so that service clients can interact with them.
The Deployment package is not used on its own. Services integrate with it, allowing the service configuration to be saved in version control.
Topic | Description |
---|---|
Getting started | Get started with the Deployment package. |
Deployment window | Use the Deployment window to deploy assets. |
Deployment Definition | Use Deployment Definitions to group assets for deployment. |
Environments | Deploy assets to specific environments. |
Integration and Programmatic use of The Deployment Window
It is possible to host your own integration in the Deployment Window by using the Deployment API
package, as the rest of the service SDKs do.
In order to integrate with the Deployment Window, follow the documentation here.
It is also possible to trigger any Deployment Window action programmatically, such as deployment, selection, etc. For examples on how to do this, follow the documentation here.
Supported packages
Files supported by the Deployment Window are created via the context menu Create > Services > Deployment Defintion in the Project Window.
Below is a list of supported services:
- com.unity.services.cloudcode (javascript) from 2.1.0
- com.unity.services.cloudcode (C#) from 2.5.0
- com.unity.remote-config from 3.2.0
- com.unity.services.economy from 3.2.1
- com.unity.services.leaderboards from 2.0.0
- com.unity.services.multiplay from 1.1.0
- com.unity.services.multiplayer
- com.unity.services.tooling
- Access Control
- Game Overrides from 1.3.0