Deploy/CDK Reference of GS2-Dictionary

The template format used when creating stacks with GS2-Deploy, and implementation examples of template output in various languages using CDK

Entity

Resources operated in Deploy process

Namespace

Namespace

A namespace is a mechanism that allows multiple uses of the same service for different purposes within a single project. 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.

Request

Resource generation request

TypeConditionRequiredDefaultValue LimitsDescription
namestring
~ 128 charsNamespace name
Namespace-specific name. Specified using alphanumeric characters, hyphens (-), underscores (_), and periods (.).
descriptionstring~ 1024 charsDescription
transactionSettingTransactionSettingTransaction settings
entryScriptScriptSettingScript setting to be executed when registering an entry
duplicateEntryScriptstring~ 1024 charsScript GRN to run when an attempt is made to re-register an entry that has already been registered
logSettingLogSettingLog output settings

GetAttr

Generation results of resources that can be obtained with the !GetAttr tag

TypeDescription
ItemNamespaceNamespace created

Implementation Example

Type: GS2::Dictionary::Namespace
Properties:
  Name: namespace-0001
  Description: null
  TransactionSetting: null
  EntryScript: null
  DuplicateEntryScript: null
  LogSetting: 
    LoggingNamespaceId: grn:gs2:ap-northeast-1:YourOwnerId:log:namespace-0001
import (
    "github.com/gs2io/gs2-golang-cdk/core"
    "github.com/gs2io/gs2-golang-cdk/dictionary"
    "github.com/openlyinc/pointy"
)

SampleStack := core.NewStack()
dictionary.NewNamespace(
    &SampleStack,
    "namespace-0001",
    dictionary.NamespaceOptions{
        LogSetting: &core.LogSetting{
            LoggingNamespaceId: "grn:gs2:ap-northeast-1:YourOwnerId:log:namespace-0001",
        },
    },
)

println(SampleStack.Yaml())  // Generate Template
class SampleStack extends \Gs2Cdk\Core\Model\Stack
{
    function __construct() {
        parent::__construct();
        new \Gs2Cdk\Dictionary\Model\Namespace_(
            stack: $this,
            name: "namespace-0001",
            options: new \Gs2Cdk\Dictionary\Model\Options\NamespaceOptions(
                logSetting: new \Gs2Cdk\Core\Model\LogSetting(
                    loggingNamespaceId: "grn:gs2:ap-northeast-1:YourOwnerId:log:namespace-0001"
                )
            )
        );
    }
}

print((new SampleStack())->yaml());  // Generate Template
class SampleStack extends io.gs2.cdk.core.model.Stack
{
    public SampleStack() {
        super();
        new io.gs2.cdk.dictionary.model.Namespace(
                this,
                "namespace-0001",
                new io.gs2.cdk.dictionary.model.options.NamespaceOptions()
                        .withLogSetting(new io.gs2.cdk.core.model.LogSetting(
                            "grn:gs2:ap-northeast-1:YourOwnerId:log:namespace-0001"
                        ))
        );
    }
}

System.out.println(new SampleStack().yaml());  // Generate Template
public class SampleStack : Gs2Cdk.Core.Model.Stack
{
    public SampleStack() {
        new Gs2Cdk.Gs2Dictionary.Model.Namespace(
            stack: this,
            name: "namespace-0001",
            options: new Gs2Cdk.Gs2Dictionary.Model.Options.NamespaceOptions
            {
                logSetting = new Gs2Cdk.Core.Model.LogSetting(
                    loggingNamespaceId: "grn:gs2:ap-northeast-1:YourOwnerId:log:namespace-0001"
                )
            }
        );
    }
}

Debug.Log(new SampleStack().Yaml());  // Generate Template
import core from "@/gs2cdk/core";
import dictionary from "@/gs2cdk/dictionary";

class SampleStack extends core.Stack
{
    public constructor() {
        super();
        new dictionary.model.Namespace(
            this,
            "namespace-0001",
            {
                logSetting: new core.LogSetting(
                    "grn:gs2:ap-northeast-1:YourOwnerId:log:namespace-0001"
                )
            }
        );
    }
}

console.log(new SampleStack().yaml());  // Generate Template
from gs2_cdk import Stack, core, dictionary

class SampleStack(Stack):

    def __init__(self):
        super().__init__()
        dictionary.Namespace(
            stack=self,
            name='namespace-0001',
            options=dictionary.NamespaceOptions(
                log_setting=core.LogSetting(
                    logging_namespace_id='grn:gs2:ap-northeast-1:YourOwnerId:log:namespace-0001',
                ),
            ),
        )

print(SampleStack().yaml())  # Generate Template

TransactionSetting

Transaction settings

Transaction settings control how transactions are executed, their consistency, asynchronous processing, and conflict avoidance mechanisms. Combining features like AutoRun, AtomicCommit, asynchronous execution using GS2-Distributor, batch application of script results, and asynchronous acquisition actions via GS2-JobQueue enables robust transaction management tailored to game logic.

TypeConditionRequiredDefaultValue LimitsDescription
enableAutoRunbool
falseWhether to automatically execute issued transactions on the server side
enableAtomicCommitbool{enableAutoRun} == true
✓*
falseWhether to commit the execution of transactions atomically
* Required if enableAutoRun is true
transactionUseDistributorbool{enableAtomicCommit} == true
✓*
falseWhether to execute transactions asynchronously
* Required if enableAtomicCommit is true
commitScriptResultInUseDistributorbool{transactionUseDistributor} == true
✓*
falseWhether to execute the commit processing of the script result asynchronously
* Required if transactionUseDistributor is true
acquireActionUseJobQueuebool{enableAtomicCommit} == true
✓*
falseWhether to use GS2-JobQueue to execute the acquire action
* Required if enableAtomicCommit is true
distributorNamespaceIdstring
“grn:gs2:{region}:{ownerId}:distributor:default”~ 1024 charsGS2-Distributor namespace GRN used for transaction execution
queueNamespaceIdstring
“grn:gs2:{region}:{ownerId}:queue:default”~ 1024 charsNamespace GRN in GS2-JobQueue used to run the transaction

ScriptSetting

Script settings

In GS2, you can associate custom scripts with microservice events and execute them. This model holds the settings for triggering script execution.

There are two main ways to execute a script: synchronous execution and asynchronous execution. Synchronous execution blocks processing until the script has finished executing. Instead, you can use the script execution result to stop the execution of the API or to tamper with the result of the API.

In contrast, asynchronous execution does not block processing until the script has finished executing. Since the script result cannot be used to stop the API execution or modify the API response, asynchronous execution does not affect the API’s response flow. For this reason, asynchronous execution is generally recommended.

There are two types of asynchronous execution methods: GS2-Script and Amazon EventBridge. By using Amazon EventBridge, you can write processing in languages other than Lua.

TypeConditionRequiredDefaultValue LimitsDescription
triggerScriptIdstring~ 1024 charsGS2-Script script GRN for synchronous execution
Must be specified in GRN format starting with “grn:gs2:”.
doneTriggerTargetTypeString Enum
enum {
  “none”,
  “gs2_script”,
  “aws”
}
“none”How to execute asynchronous scripts
Specifies the type of script to use for asynchronous execution.
You can choose from “Do not use asynchronous execution scripts (none)”, “Use GS2-Script (gs2_script)”, and “Use Amazon EventBridge (aws)”.
Enumerator String DefinitionDescription
“none”None
“gs2_script”GS2-Script
“aws”Amazon EventBridge
doneTriggerScriptIdstring{doneTriggerTargetType} == “gs2_script”~ 1024 charsGS2-Script script GRN for Asynchronous Execution
Must be specified in GRN format starting with “grn:gs2:”.

* Enabled if doneTriggerTargetType is “gs2_script”
doneTriggerQueueNamespaceIdstring{doneTriggerTargetType} == “gs2_script”~ 1024 charsGS2-JobQueue namespace GRN to execute asynchronous execution scripts
If you want to execute asynchronous execution scripts via GS2-JobQueue instead of executing them directly, specify the GS2-JobQueue namespace GRN.
There is little reason to use GS2-JobQueue, so you don’t need to specify it unless you have a specific reason.

* Enabled if doneTriggerTargetType is “gs2_script”

LogSetting

Log setting

This type manages log output settings. This type holds the identifier of the log namespace used to output log data. The log namespace ID specifies the GS2-Log namespace to aggregate and store the log data. Through this setting, API request and response log data under this namespace will be output to the target GS2-Log. GS2-Log provides logs in real time, which can be used for system monitoring, analysis, debugging, etc.

TypeConditionRequiredDefaultValue LimitsDescription
loggingNamespaceIdstring
~ 1024 charsGS2-Log namespace GRN to output logs
Must be specified in GRN format starting with “grn:gs2:”.

CurrentEntryMaster

Currently Active Master Data

Currently active master data describing the entry model definitions within the namespace. GS2 uses JSON format files for managing master data. By uploading these files, the master data settings are updated on the server.

To create JSON files, GS2 provides a master data editor within the management console. Additionally, you can create tools better suited for operating your game and export JSON files in the appropriate format.

Request

Resource generation request

TypeConditionRequiredDefaultValue LimitsDescription
namespaceNamestring
~ 128 charsNamespace name
Namespace-specific name. Specified using alphanumeric characters, hyphens (-), underscores (_), and periods (.).
modeString Enum
enum {
  “direct”,
  “preUpload”
}
“direct”Update mode
Enumerator String DefinitionDescription
“direct”Directly update master data
“preUpload”Upload master data and then update
settingsstring{mode} == “direct”
✓*
~ 5242880 charsMaster Data
* Required if mode is “direct”
uploadTokenstring{mode} == “preUpload”
✓*
~ 1024 charsToken used to reflect results after upload
* Required if mode is “preUpload”

GetAttr

Generation results of resources that can be obtained with the !GetAttr tag

TypeDescription
ItemCurrentEntryMasterUpdated Currently Active Entry Model Master Data

Implementation Example

Type: GS2::Dictionary::CurrentEntryMaster
Properties:
  NamespaceName: namespace-0001
  Mode: direct
  Settings: {
    "version": "2020-04-30",
    "entryModels": [
      {
        "name": "monster-0001",
        "metadata": "MONSTER-0001"
      },
      {
        "name": "monster-0002",
        "metadata": "MONSTER-0002"
      }
    ]
  }
  UploadToken: null
import (
    "github.com/gs2io/gs2-golang-cdk/core"
    "github.com/gs2io/gs2-golang-cdk/dictionary"
    "github.com/openlyinc/pointy"
)

SampleStack := core.NewStack()
dictionary.NewNamespace(
    &SampleStack,
    "namespace-0001",
    dictionary.NamespaceOptions{},
).MasterData(
    []dictionary.EntryModel{
        dictionary.NewEntryModel(
            "monster-0001",
            dictionary.EntryModelOptions{
                Metadata: pointy.String("MONSTER-0001"),
            },
        ),
        dictionary.NewEntryModel(
            "monster-0002",
            dictionary.EntryModelOptions{
                Metadata: pointy.String("MONSTER-0002"),
            },
        ),
    },
)

println(SampleStack.Yaml())  // Generate Template
class SampleStack extends \Gs2Cdk\Core\Model\Stack
{
    function __construct() {
        parent::__construct();
        (new \Gs2Cdk\Dictionary\Model\Namespace_(
            stack: $this,
            name: "namespace-0001"
        ))->masterData(
            [
                new \Gs2Cdk\Dictionary\Model\EntryModel(
                    name:"monster-0001",
                    options: new \Gs2Cdk\Dictionary\Model\Options\EntryModelOptions(
                        metadata:"MONSTER-0001"
                    )
                ),
                new \Gs2Cdk\Dictionary\Model\EntryModel(
                    name:"monster-0002",
                    options: new \Gs2Cdk\Dictionary\Model\Options\EntryModelOptions(
                        metadata:"MONSTER-0002"
                    )
                )
            ]
        );
    }
}

print((new SampleStack())->yaml());  // Generate Template
class SampleStack extends io.gs2.cdk.core.model.Stack
{
    public SampleStack() {
        super();
        new io.gs2.cdk.dictionary.model.Namespace(
            this,
            "namespace-0001"
        ).masterData(
            Arrays.asList(
                new io.gs2.cdk.dictionary.model.EntryModel(
                    "monster-0001",
                    new io.gs2.cdk.dictionary.model.options.EntryModelOptions()
                        .withMetadata("MONSTER-0001")
                ),
                new io.gs2.cdk.dictionary.model.EntryModel(
                    "monster-0002",
                    new io.gs2.cdk.dictionary.model.options.EntryModelOptions()
                        .withMetadata("MONSTER-0002")
                )
            )
        );
    }
}

System.out.println(new SampleStack().yaml());  // Generate Template
public class SampleStack : Gs2Cdk.Core.Model.Stack
{
    public SampleStack() {
        new Gs2Cdk.Gs2Dictionary.Model.Namespace(
            stack: this,
            name: "namespace-0001"
        ).MasterData(
            new Gs2Cdk.Gs2Dictionary.Model.EntryModel[] {
                new Gs2Cdk.Gs2Dictionary.Model.EntryModel(
                    name: "monster-0001",
                    options: new Gs2Cdk.Gs2Dictionary.Model.Options.EntryModelOptions
                    {
                        metadata = "MONSTER-0001"
                    }
                ),
                new Gs2Cdk.Gs2Dictionary.Model.EntryModel(
                    name: "monster-0002",
                    options: new Gs2Cdk.Gs2Dictionary.Model.Options.EntryModelOptions
                    {
                        metadata = "MONSTER-0002"
                    }
                )
            }
        );
    }
}

Debug.Log(new SampleStack().Yaml());  // Generate Template
import core from "@/gs2cdk/core";
import dictionary from "@/gs2cdk/dictionary";

class SampleStack extends core.Stack
{
    public constructor() {
        super();
        new dictionary.model.Namespace(
            this,
            "namespace-0001",
        ).masterData(
            [
                new dictionary.model.EntryModel(
                    "monster-0001",
                    {
                        metadata: "MONSTER-0001"
                    }
                ),
                new dictionary.model.EntryModel(
                    "monster-0002",
                    {
                        metadata: "MONSTER-0002"
                    }
                )
            ]
        );
    }
}

console.log(new SampleStack().yaml());  // Generate Template
from gs2_cdk import Stack, core, dictionary

class SampleStack(Stack):

    def __init__(self):
        super().__init__()
        dictionary.Namespace(
            stack=self,
            name="namespace-0001",
        ).master_data(
            entry_models=[
                dictionary.EntryModel(
                    name='monster-0001',
                    options=dictionary.EntryModelOptions(
                        metadata = 'MONSTER-0001'
                    ),
                ),
                dictionary.EntryModel(
                    name='monster-0002',
                    options=dictionary.EntryModelOptions(
                        metadata = 'MONSTER-0002'
                    ),
                ),
            ],
        )

print(SampleStack().yaml())  # Generate Template

EntryModel

Entry Model

The Entry Model is the entity to be recorded in the index. This section defines what kind of entities can be recorded in the index.

TypeConditionRequiredDefaultValue LimitsDescription
entryModelIdstring
✓*
~ 1024 charsEntry Model GRN
* Automatically configured on the server
namestring
~ 128 charsEntry Model Name
metadatastring~ 2048 charsMetadata
Arbitrary values can be set in the metadata.
Since they do not affect GS2’s behavior, they can be used to store information used in the game.