Deploy/CDK Reference of GS2-Dictionary
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
| Type | Condition | Required | Default | Value Limits | Description | |
|---|---|---|---|---|---|---|
| name | string | ✓ | ~ 128 chars | Namespace name Namespace-specific name. Specified using alphanumeric characters, hyphens (-), underscores (_), and periods (.). | ||
| description | string | ~ 1024 chars | Description | |||
| transactionSetting | TransactionSetting | Transaction settings | ||||
| entryScript | ScriptSetting | Script setting to be executed when registering an entry | ||||
| duplicateEntryScript | string | ~ 1024 chars | Script GRN to run when an attempt is made to re-register an entry that has already been registered | |||
| logSetting | LogSetting | Log output settings |
GetAttr
Generation results of resources that can be obtained with the !GetAttr tag
| Type | Description | |
|---|---|---|
| Item | Namespace | Namespace 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-0001import (
"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 Templatepublic 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 Templateimport 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 TemplateTransactionSetting
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.
| Type | Condition | Required | Default | Value Limits | Description | |
|---|---|---|---|---|---|---|
| enableAutoRun | bool | ✓ | false | Whether to automatically execute issued transactions on the server side | ||
| enableAtomicCommit | bool | {enableAutoRun} == true | ✓* | false | Whether to commit the execution of transactions atomically * Required if enableAutoRun is true | |
| transactionUseDistributor | bool | {enableAtomicCommit} == true | ✓* | false | Whether to execute transactions asynchronously * Required if enableAtomicCommit is true | |
| commitScriptResultInUseDistributor | bool | {transactionUseDistributor} == true | ✓* | false | Whether to execute the commit processing of the script result asynchronously * Required if transactionUseDistributor is true | |
| acquireActionUseJobQueue | bool | {enableAtomicCommit} == true | ✓* | false | Whether to use GS2-JobQueue to execute the acquire action * Required if enableAtomicCommit is true | |
| distributorNamespaceId | string | ✓ | “grn:gs2:{region}:{ownerId}:distributor:default” | ~ 1024 chars | GS2-Distributor namespace GRN used for transaction execution | |
| queueNamespaceId | string | ✓ | “grn:gs2:{region}:{ownerId}:queue:default” | ~ 1024 chars | Namespace 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.
| Type | Condition | Required | Default | Value Limits | Description | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| triggerScriptId | string | ~ 1024 chars | GS2-Script script GRN
for synchronous execution Must be specified in GRN format starting with “grn:gs2:”. | |||||||||||
| doneTriggerTargetType | String 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)”.
| ||||||||||
| doneTriggerScriptId | string | {doneTriggerTargetType} == “gs2_script” | ~ 1024 chars | GS2-Script script GRN
for Asynchronous Execution Must be specified in GRN format starting with “grn:gs2:”. * Enabled if doneTriggerTargetType is “gs2_script” | ||||||||||
| doneTriggerQueueNamespaceId | string | {doneTriggerTargetType} == “gs2_script” | ~ 1024 chars | GS2-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.
| Type | Condition | Required | Default | Value Limits | Description | |
|---|---|---|---|---|---|---|
| loggingNamespaceId | string | ✓ | ~ 1024 chars | GS2-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.
Note
Please refer to Master Data Reference of GS2-Dictionary for the JSON file format.Request
Resource generation request
| Type | Condition | Required | Default | Value Limits | Description | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| namespaceName | string | ✓ | ~ 128 chars | Namespace name Namespace-specific name. Specified using alphanumeric characters, hyphens (-), underscores (_), and periods (.). | ||||||||
| mode | String Enum enum { “direct”, “preUpload” } | ✓ | “direct” | Update mode
| ||||||||
| settings | string | {mode} == “direct” | ✓* | ~ 5242880 chars | Master Data * Required if mode is “direct” | |||||||
| uploadToken | string | {mode} == “preUpload” | ✓* | ~ 1024 chars | Token used to reflect results after upload * Required if mode is “preUpload” |
GetAttr
Generation results of resources that can be obtained with the !GetAttr tag
| Type | Description | |
|---|---|---|
| Item | CurrentEntryMaster | Updated 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: nullimport (
"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 Templatepublic 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 Templateimport 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 TemplateEntryModel
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.
| Type | Condition | Required | Default | Value Limits | Description | |
|---|---|---|---|---|---|---|
| entryModelId | string | ✓* | ~ 1024 chars | Entry Model GRN * Automatically configured on the server | ||
| name | string | ✓ | ~ 128 chars | Entry Model Name | ||
| metadata | string | ~ 2048 chars | Metadata 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. |