Upgrading to the latest version of the Tenant SDK should be simple if you use the upgrade utility. It helps you to find and apply a new version of the Tenant SDK.
4.0.0of the Tenant SDK. If you are updating from an earlier version you need to contact us before proceeding.
Start by signing in to your Azure Portal with an account that has access to the subscription where the Tenant SDK resources resides.
Azure Cloud Shell (see screenshot below).
If you have not used the Azure Cloud Shell before, you will be prompted to create a new Azure file share for persisting files.
Maximize the window and select
Bash in the shell language selector.
First, make sure your active subscription is the same as the one that contains the Tenant SDK resources. Execute the following line in the terminal to show the active subscription:
If your active subscription is not the correct one, change the active subscription by issuing the command below and entering the correct subscription id:
Execute the following line in the terminal:
curl https://weavy.blob.core.windows.net/releases/wdm/update.sh > update.sh
This downloads a copy of the
Bash script used to search for and deploy updated versions.
Issue the following command to set execute permissions for the
chmod +x ./update.sh
Then execute the script file by issuing:
The tool will try to locate the web app that is running the Tenant SDK. Verify that the app name is correct and continue by entering y.
During the next step, the tool will verify the current version of your Tenant SDK and determine if there is an update available. If not, you will get a message saying that you are already using the latest version. In that case, feel free to close the terminal and cancel the upgrade.
If there is an update available you will be prompted to take a backup of the database before performing the update. Please make sure to do that if you didn't before.
Again, continue the update by pressing
y. This will start the download and deployment of the updated package.
When the update is done you will be notified, and after that you can close the terminal.
Navigate to your Deployment Manager in a browser to make sure everything is running normally.