/tags/cdk/ Recent content in CDK on Game Server Services | Docs Hugo en /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.