Google Game Servers Game Services Game Server Config

This page shows how to write Terraform for Game Servers Game Services Game Server Config and write them securely.

google_game_services_game_server_config (Terraform)

The Game Services Game Server Config in Game Servers can be configured in Terraform with the resource name google_game_services_game_server_config. The following sections describe 1 example of how to use the resource and its parameters.

Example Usage from GitHub

main.tf#L7
resource "google_game_services_game_server_config" "this" {
  config_id     = var.config_id
  deployment_id = var.deployment_id
  description   = var.description
  labels        = var.labels
  location      = var.location

Review your Terraform file for Google best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).

Parameters

A unique id for the deployment config.

A unique id for the deployment.

The description of the game server config.

  • id optional computed - string
  • labels optional - map from string to string

The labels associated with this game server config. Each label is a key-value pair.

Location of the Deployment.

  • name optional computed - string

The resource name of the game server config, in the form: 'projects/[project_id]/locations/[location]/gameServerDeployments/[deployment_id]/configs/[config_id]'.

  • project optional computed - string
  • fleet_configs list block

    The fleet spec, which is sent to Agones to configure fleet. The spec can be passed as inline json but it is recommended to use a file reference instead. File references can contain the json or yaml format of the fleet spec. Eg: fleet_spec = jsonencode(yamldecode(file("fleet_configs.yaml"))) fleet_spec = file("fleet_configs.json") The format of the spec can be found : 'https://agones.dev/site/docs/reference/fleet/'.

    • name optional computed - string

    The name of the FleetConfig.

  • scaling_configs list block

    Fleet autoscaler spec, which is sent to Agones. Example spec can be found : https://agones.dev/site/docs/reference/fleetautoscaler/

    The name of the ScalingConfig

    • schedules list block

      The duration for the cron job event. The duration of the event is effective after the cron job's start time. A duration in seconds with up to nine fractional digits, terminated by 's'. Example: "3.5s".

      The cron definition of the scheduled event. See https://en.wikipedia.org/wiki/Cron. Cron spec specifies the local time as defined by the realm.

      The end time of the event. A timestamp in RFC3339 UTC "Zulu" format, accurate to nanoseconds. Example: "2014-10-02T15:01:23.045123456Z".

      The start time of the event. A timestamp in RFC3339 UTC "Zulu" format, accurate to nanoseconds. Example: "2014-10-02T15:01:23.045123456Z".

    • selectors list block
      • labels optional - map from string to string

      Set of labels to group by.

  • timeouts single block

Explanation in Terraform Registry

A game server config resource. Configs are global and immutable. To get more information about GameServerConfig, see:

Frequently asked questions

What is Google Game Servers Game Services Game Server Config?

Google Game Servers Game Services Game Server Config is a resource for Game Servers of Google Cloud Platform. Settings can be wrote in Terraform.

Where can I find the example code for the Google Game Servers Game Services Game Server Config?

For Terraform, the niveklabs/google source code example is useful. See the Terraform Example section for further details.

security-icon

Automate config file reviews on your commits

Fix issues in your infrastructure as code with auto-generated patches.