/tags/deploy/ Recent content in Deploy on Game Server Services | Docs Hugo en /articles/tech/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /articles/tech/deploy/ This is the format specification of the template file used when creating a stack in GS2-Deploy. It can be written in JSON or YAML format. Types of sections A template consists of the following sections. Section Required Description GS2TemplateFormatVersion ✓ Specifies the format of the template. Currently only 2019-05-01 can be defined. Description You can fill in the description and other information about the template. Globals This section defines the Alias attribute (string replacement specification). /get_start/tutorial/setup_credential/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /get_start/tutorial/setup_credential/deploy/ Adding users and credentials (authentication information) can be done from the GS2-Identifier administration screen, but it is easier with GS2-Deploy. GS2-Deploy is a service designed to realize continuous delivery. It allows automatic construction of resources using code written in YAML format. For example, if you create a stack using a template for adding a new user, you can automatically add a new user to GS2-Identifier. About Stacks GS2-Deploy actually operates resources of each service based on a template (which describes how to operate and build resources in GS2). /overview/workflow/setup_gs2_resources/automation_setup/ Mon, 01 Jan 0001 00:00:00 +0000 /overview/workflow/setup_gs2_resources/automation_setup/ Setup using the management console is attractive because it is easy to perform. However, you must despair when you receive an order to “create another of the same environment”. Game development typically requires multiple server environments: a development environment, a test environment, and a production environment. It is impossible to configure GS2 in each of them by repeating the same operation in the management console without making mistakes. GS2-Deploy GS2 provides GS2-Deploy, a microservice for creating environments. /get_start/tutorial/setup_account/ Mon, 01 Jan 0001 00:00:00 +0000 /get_start/tutorial/setup_account/ To start using the GS2-Account service, you need to add a namespace. Namespace (namespace) is a mechanism to allow the same service to be used for different purposes within a single project. Within different namespaces, the same service is treated as a completely different data space. Now, using the sample template, add game-0001 to the GS2-Account namespace name and issue the encryption key that will be used to authenticate the account and make it possible to create a new account. /api_reference/account/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/account/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/ad_reward/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/ad_reward/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/buff/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/buff/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the Namespace differs, the data is treated as a completely independent data space. Therefore, you must create a Namespace before you can start using each service. /api_reference/chat/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/chat/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the Namespace differs, the data is treated as a completely independent data space. Therefore, you must create a Namespace before you can start using each service. /api_reference/datastore/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/datastore/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/dictionary/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/dictionary/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/distributor/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/distributor/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/enchant/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/enchant/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/enhance/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/enhance/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/exchange/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/exchange/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/experience/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/experience/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/formation/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/formation/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/friend/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/friend/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/gateway/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/gateway/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/grade/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/grade/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/guard/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/guard/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/guild/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/guild/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/identifier/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/identifier/deploy/ Entities Resources managed by the Deploy operation Identifier Credential Credentials used to access the GS2 API. A credential consists of a client ID and a client secret, and access using the credential is restricted based on the privileges of the user who owns the credential. Request Resource creation and update requests Type Condition Required Default Value Limits Description userName string ✓ ~ 128 chars User NameThe name of the GS2-Identifier user who owns this credential. /api_reference/idle/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/idle/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the Namespace differs, the data is treated as a completely independent data space. Therefore, you must create a Namespace before you can start using each service. /api_reference/inbox/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/inbox/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/inventory/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/inventory/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/job_queue/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/job_queue/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/key/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/key/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the Namespace differs, the data is treated as a completely independent data space. Therefore, you must create a Namespace before you can start using each service. /api_reference/limit/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/limit/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/lock/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/lock/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the Namespace differs, the data is treated as a completely independent data space. Therefore, you must create a Namespace before you can start using each service. /api_reference/log/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/log/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the Namespace differs, the data is treated as a completely independent data space. Therefore, you must create a Namespace before you can start using each service. /api_reference/login_reward/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/login_reward/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/lottery/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/lottery/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/matchmaking/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/matchmaking/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/mega_field/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/mega_field/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/mission/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/mission/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/money/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/money/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/money2/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/money2/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/news/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/news/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/quest/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/quest/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/ranking/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/ranking/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/ranking2/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/ranking2/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/realtime/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/realtime/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/schedule/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/schedule/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/script/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/script/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/season_rating/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/season_rating/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/serial_key/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/serial_key/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/showcase/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/showcase/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/skill_tree/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/skill_tree/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/stamina/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/stamina/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/state_machine/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/state_machine/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service. /api_reference/version/deploy/ Mon, 01 Jan 0001 00:00:00 +0000 /api_reference/version/deploy/ Entities Resources managed by the Deploy operation Namespace Namespace A Namespace allows multiple independent instances of the same service within a single project by separating data spaces and usage contexts. Each GS2 service is managed on a per-namespace basis. Even when using the same service, if the namespace differs, the data is treated as a completely independent data space. Therefore, you must create a namespace before you can start using each service.