Iterating over your IMS integration by uploading your game image and updating an allocation can be time consuming. We just released a mock Payload Local API server that you can use to test your game server integration locally. This means faster development and testing, and ultimately a faster integration with our services.
Allocation region 🌍
Gone are the days of remembering and manually entering cluster IDs. Creating an allocation just got easier. Now you just select from your available regions in the allocation form.
Clusters IDs are still used on the API side, so we have included the Cluster IDs in the UI making it easy to look up which cluster an allocation is running on.
Image manager API 📷
Some of you like to build out your own internal tooling that allows you to deploy your game servers to IMS. One frequently requested feature was an API to view and manage game server images.
Today we have opened up access to the Game Image Inventory API, this allows you to perform common operations: list, get, and delete. It uses the same authentication flow as the IMS zeuz APIs so should plug straight into your workflows.
You can find out more in the OpenAPI spec
More consistent CLI output 💅
We know the IMS CLI hasn't always been the most consistent, so we recently overhauled the output over every command, resulting in a cleaner, more consistent output.
- Log lines are categorized into Info, Warning, Success, and Error, and color is used to make these easy to differentiate.
- The mix use of Lists and Tables has been replaced with just Table outputs. These tables have been designed to closely match the UI and be more consistent across commands
- JSON output-type support has been added to all commands where appropriate (for example
- Spinners are used to indicate tasks in progress.
When using the JSON output type we still output the pretty "human" log lines, these are forwarded to stderr so that your terminal still displays them, but they do not impact your ability to parse the JSON output which is forwarded to stdout.
Additionally, since the color and styled output may interfere with CI tooling such as Jenkins we default to
plaintext output when the
--ci flag is present. You can override this behavior with the
Many backend engineers want to deploy game servers as part of their continuous integration (CI) pipelines. For example, the pipeline publishes a gameserver image, then automatically configure an allocation to use it.
The new CLI command
ims orchestration allocation update-image will update the image of an allocation, while keeping all other configurations the same.