# Configuration as code

> Learn how to manage Unity Gaming Services configurations in files, deploy to environments, and automate processes using the UGS CLI and Environments API.

Use configuration-as-code workflows to manage service configurations for your project the same as code, and eliminate manual environment setup across your development pipeline, including the following:

* Version configuration files using source control tools.
* Deploy configurations to different [environments](/services/service-environments.md) using the [UGS CLI](/services/ugs-cli-introduction.md) or [Deployment package](https://docs.unity3d.com/Packages/com.unity.services.deployment@latest/index.html?subfolder=/manual/index.html).
* Fetch configuration files from the Dashboard using the [UGS CLI](/services/ugs-cli-introduction.md).
* Integrate processes into your CI/CD pipeline.
* Reuse configuration files across projects and organizations.

If you use the Unity Editor, you can author compatible configurations with packages such as [Remote Config](/remote-config.md) and [Cloud Code](/cloud-code.md), and deploy using the [Deployment window](https://docs.unity3d.com/Packages/com.unity.services.deployment@latest/index.html?subfolder=/manual/deployment_window.html).

[Unity Gaming Services CLI](/services/ugs-cli-introduction.md): Manage Unity Gaming Services (UGS) configurations from the command line.
[Environments](/services/service-environments.md): Use logical partitions to organize your service configurations for testing, staging, and production workflows.
[Environments API](/services/environments-api.md): Manage logical data partitions using the Environments API.
