GS2-Freeze API Reference

A microservice that provides an interface to fix the version of GS2 microservices

GS2 is updated daily, and we provide a feature to fix the code base to minimize the impact of those updates. This microservice provides the ability to fix the version, but support for bug fixes and vulnerabilities is only provided as a difference from the latest code base. Therefore, even if you use this feature, please make sure to follow the latest code base at least once a month (recommended weekly).

The central concept of GS2-Freeze is the “Stage”. A stage represents “a set of GS2 microservice versions frozen at a specific point in time”.

By specifying the stage to use when calling GS2 APIs, the game client and server can use the version of the microservices frozen on that stage.

The operation of updating the version of a stage is called “Promote”. When promote is executed, the version frozen on the source stage is copied to the target stage. For example, “promoting the version of the staging stage to the production stage” reflects a verified version to production.

If a problem is discovered after promotion, you can execute a “Rollback” to revert to the previous version.

By using sortNumber, you can arrange multiple stages as a hierarchy such as “development”, “staging”, and “production”. The sort order is used for the display order in the management console and as reference information when selecting the target of a promote.