Upgrade from Previous Versions
Upgrading the Genvid MILE SDK from one version to another may include some manual steps. This page includes any steps required to update to version 1.45.0 from the last version. If you’re upgrading an older version of the SDK, start with any special upgrade instructions for your version found here.
General Upgrade Instructions
Upgrade the Genvid MILE SDK
Important
Since version 1.33, the Genvid Toolbox package no longer depends on the Azure CLI. Instead, it uses the standalone Azure CLI Installer to avoid some dependency conflicts. When upgrading, you might get some conflict errors. However, the installation favors the last package, so your Toolbox installation will be successful despite these messages. As a precaution, you might want to remove the Azure CLI package and its dependencies and use the standalone Azure CLI installer instead.
To set up the new SDK locally:
Install the new SDK.
Run the Python script to install the Genvid Toolbox.
py install-toolbox.py
Run the Genvid Bastion script to update your bastion.
genvid-bastion reinstall --reconfigure --resetconfig -b {mybastion} -uml
If you have a
local
cluster running, you should update the configuration of the cluster by running.genvid-sdk setup genvid-sdk load-config-sdk
Update Your Broadcast Website
If you used code from the samples we provide in your own project, note that we recently enforced a best practice concerning service discovery using consul in those samples. You should check again the samples and update your project accordingly. We invite you to use the consul health api instead of the catalog api to fetch the url of your services, since it is more likely that the url will point to a healthy service.
Update Your Game
To update your game without applying new features, just
replace the old genvid.dll
from the previous SDK with the one
from the new SDK. The old plugins and integration should work as-is,
with the exception of the specific upgrade instructions below.
Attention
Always follow the full upgrade path for the Genvid SDK version you’re using. For example: If you’re upgrading from version 1.6.0 to 1.10.0, start by upgrading from 1.6.0 to 1.7.0 then continue with each version.
See the full list of upgrade instructions for your specific version.
Warning
The Genvid Plugin for Unity and the Genvid Plugin for Unreal Engine are not guaranteed to work with SDK versions older than they are. If you’re having any issues using a plugin, verify that you’re using them with a matching or more recent version of the SDK.
Upgrade the Javascript API
You should also upgrade the Genvid JavaScript API on your website.
Update Your Cluster
We strongly recommend keeping your old clusters as-is and creating a new one for the update.
To create a new cloud-based cluster, follow the standard instructions:
Set up a new wingame AMI that matches the new version.
To create a new local cluster, follow the standard instructions listed in the Initializing a Local Cluster section.
Once you have replaced all your clusters, you can remove the old SDK repositories from the Modules Section page.
Updating an Existing Cluster
Warning
Updating your cluster can replace all your instances and even erase your current configuration. We recommend not updating a live cluster. If you do, carefully check the changes before applying the plan.
You can update the module used to build your cluster by clicking on Reimport Module in the module section of your cluster infrastructure, then select the module new version and import it. Finally, click apply in the Terraform section.
Note
Some changes can take time to propagate to AWS. This is especially true for IAM roles and policies, which could then create some conflicts when recreated. Re-applying the Terraform plan should fix the problem.
Update Genvid SDK Samples
Along with your own project, make sure you update any of the Genvid SDK samples you’ve previously installed.
Upgrade from 1.44.0 to 1.45.0
Upgrading from Older Versions
Note
If there aren’t specific instructions listed for a version, then there aren’t any special steps for upgrading that version.
- Upgrade from 1.0.0 to 1.1.0
- Upgrade from 1.2.0 to 1.3.0
- Upgrade from 1.3.0 to 1.4.0
- Upgrade from 1.6.0 to 1.7.0
- Upgrade from 1.7.0 to 1.8.0
- Upgrade from 1.8.0 to 1.9.0
- Upgrade from 1.9.0 to 1.10.0
- Upgrade from 1.11.0 to 1.12.0
- Upgrade from 1.12.0 to 1.13.0
- Upgrade from 1.13.0 to 1.14.0
- Upgrade from 1.15.0 to 1.15.1
- Upgrade from 1.16.0 to 1.17.0
- Upgrade from 1.17.0 to 1.18.0
- Upgrade from 1.18.0 to 1.19.0
- Upgrade from 1.19.0 to 1.20.0
- Upgrade from 1.20.1 to 1.21.0
- Upgrade from 1.21.2 to 1.22.0
- Upgrade from 1.22.0 to 1.23.0
- Upgrade from 1.23.0 to 1.24.0
- Upgrade from 1.24.0 to 1.25.0
- Upgrade from 1.25.0 to 1.26.0
- Upgrade from 1.26.0 to 1.27.0
- Upgrade from 1.27.0 to 1.27.1
- Upgrade from 1.27.0 to 1.28.1
- Upgrade from 1.28.0 to 1.29.0
- Upgrade from 1.29.0 to 1.30.0
- Upgrade from 1.30.0 to 1.31.0
- Upgrade from 1.31.0 to 1.32.0
- Upgrade from 1.32.0 to 1.33.0
- Upgrade from 1.33.0 to 1.34.0
- Upgrade from 1.35.0 to 1.36.0
- Upgrade from 1.36.0 to 1.37.0
- Upgrade from 1.37.0 to 1.38.0
- Upgrade from 1.38.0 to 1.39.0
- Upgrade from 1.39.0 to 1.40.0
- Upgrade from 1.40.0 to 1.41.0
- Upgrade from 1.41.0 to 1.42.0
- Upgrade from 1.42.0 to 1.43.0
- Upgrade from 1.43.0 to 1.44.0