mirror of
https://github.com/Unleash/unleash.git
synced 2024-10-28 19:06:12 +01:00
62a7633ed5
Upgrading to 5.7 and above from earlier versions is a little problematic. Let's document it. --------- Co-authored-by: Gastón Fournier <gaston@getunleash.io>
166 lines
9.3 KiB
Markdown
166 lines
9.3 KiB
Markdown
---
|
|
title: Upgrading Unleash
|
|
---
|
|
import VideoContent from '@site/src/components/VideoContent.jsx'
|
|
|
|
Generally, the intention is that `unleash-server` should always provide support for clients one major version lower than the current one. This should make it possible to upgrade `unleash` gradually.
|
|
|
|
## Upgrading to 5.7 and later from versions < 5.6.11
|
|
|
|
When running on high-availability (multiple Unleash instances), upgrading from versions lower than 5.6.11 to version 5.7 or higher will cause a temporary UI unavailability while old versions and new versions are both serving traffic, due to a compatibility issue. If you can afford having a small period of time with the UI unavailable (note the SDKs will not be affected), then you can safely upgrade.
|
|
|
|
If you rather want to avoid that, you should first update to 5.6.11 and ensure all your Unleash instances are running 5.6.11 before upgrading to 5.7 or later. Any Unleash instances left on earlier versions after the backing database has been updated will continue to work, but you will not be able to log in to them, but the SDKs will continue working fine.
|
|
|
|
Once you have upgraded to version 5.7 and above, you can no longer downgrade to versions before 5.7 without manual changes to the database.
|
|
|
|
## Upgrading directly from v3.x to v5.x
|
|
|
|
<VideoContent videoUrls={["https://www.youtube.com/embed/qmusq_9mE2E"]}/>
|
|
|
|
Ivar Østhus, Unleash CTO and Co-Founder, demonstrates how to update Unleash 3.x to Unleash 5.x in just a few minutes with no downtime. You can also [watch this on YouTube with a transcript](https://www.youtube.com/watch?v=qmusq_9mE2E&cc_load_policy=1).
|
|
|
|
## Upgrading from v4.x to v5.x {#upgrading-from-v4x-to-v5x}
|
|
|
|
Unleash v5 was released on April 27th, 2023. It contains a few breaking changes.
|
|
|
|
### Requires Node.js version 18+
|
|
|
|
Unleash v5 drops support Node.js versions below 18, which is the current active LTS at the time of release. Unleash v4 officially supported Node.js v14 and v16, but both of these will reach end of life in 2023.
|
|
|
|
### The Google Authenticator provider for SSO has been removed
|
|
|
|
The Google Authenticator provider is now hidden by default. We recommend using [OpenID Connect](../../how-to/how-to-add-sso-open-id-connect.md) instead.
|
|
|
|
However, if you are running a self hosted version of Unleash and you need to temporarily re-enable Google SSO, you can do so by setting the `GOOGLE_AUTH_ENABLED` environment variable to `true`. If you're running a hosted version of Unleash, you'll need to reach out to us and ask us to re-enable the flag. However, the ability to do this will be removed in a future release and this is not safe to depend on.
|
|
|
|
This provider was deprecated in v4.
|
|
|
|
### Default database password
|
|
|
|
The Unleash default database password is now `password` instead of `passord`. Turns out that the Norwegian word for password is too similar to the English word, and that people would think it was a typo.
|
|
|
|
This should only impact dev builds and initial setup. You should never use the default password in any production environments.
|
|
|
|
### The /api/admin/features API is gone
|
|
|
|
Most of the old features API was deprecated in v4.3 and superseded by the project API instead. In v5, the deprecated parts have been completely removed. The only operations on that API that are still active are the operations to add or remove a tag from a feature toggle.
|
|
|
|
### Error message structure
|
|
|
|
Some of Unleash's API error messages have changed their structure. Specifically, this applies to error messages generated by our OpenAPI validation layer. However, only their structure has changed (and they now contain more human-friendly messages); the error codes should still be the same.
|
|
|
|
Previously, they would look like this:
|
|
|
|
``` json
|
|
{
|
|
"error": "Request validation failed",
|
|
"validation": [
|
|
{
|
|
"keyword": "type",
|
|
"dataPath": ".body.parameters",
|
|
"schemaPath": "#/components/schemas/addonCreateUpdateSchema/properties/parameters/type",
|
|
"params": {
|
|
"type": "object"
|
|
},
|
|
"message": "should be object"
|
|
}
|
|
]
|
|
}
|
|
```
|
|
|
|
Now they look like this instead, and are more in line with the rest of Unleash's error messages.
|
|
|
|
```json
|
|
{
|
|
"id": "37a1765f-a5a0-4371-8aa2-341f331579f9",
|
|
"name": "ValidationError",
|
|
"message": "Request validation failed: the payload you provided doesn't conform to the schema. Check the `details` property for a list of errors that we found.",
|
|
"details": [
|
|
{
|
|
"description": "The .parameters property should be object. You sent [].",
|
|
"path": "parameters"
|
|
}
|
|
]
|
|
}
|
|
```
|
|
|
|
As such, if you're relying on the specifics of the error structure for those API errors, you might need to update your handling.
|
|
|
|
## Upgrading from v3.x to v4.x {#upgrading-from-v3x-to-v4x}
|
|
|
|
Before you upgrade we strongly recommend that you take a full [database backup](database-backup), to make sure you can downgrade to version 3.
|
|
|
|
You can also read the highlights of **[what's new in v4](/user_guide/v4-whats-new)**.
|
|
|
|
### 1. All API calls now require a token. {#1-all-api-calls-now-requires-token}
|
|
|
|
If you are upgrading from Unleash Open-Source v3 client SDKs did not need to use an API token in order to connect to Unleash-server. Starting from v4 we have back-ported the API token handling for Enterprise in to the Open-Source version. This means that all client SDKs now need to use a client token in order to connect to Unleash.
|
|
|
|
Read more in the [API token documentation](../../how-to/how-to-create-api-tokens.mdx).
|
|
|
|
### 2. Configuring Unleash {#2-configuring-unleash}
|
|
|
|
We have done a lot of changes to the options you can pass in to Unleash. If you are manually configuring Unleash you should have a look on the updated [configuring Unleash documentation](./configuring-unleash.md)
|
|
|
|
### 3. Role-based Access Control (RBAC) {#3-role-based-access-control-rbac}
|
|
|
|
We have implemented RBAC in Unleash v4. This has totally changed the permission system in Unleash.
|
|
|
|
**Required actions:** If you have implemented "custom authentication" for your users you will need to make changes to your integration:
|
|
|
|
- _extendedPermissions_ option has been removed. You can no longer specify custom permission per-user basis. All "logged_in users" must belong to a "root" role. This can be "Admin", "Editor" or "Viewer". This is taken care of when you create new users via userService.
|
|
- All "logged-in users" needs to be defined in Unleash and have a unique ID. This can be achieved by calling "createUser" on "userService".
|
|
|
|
Code example:
|
|
|
|
```js
|
|
const user = userService.loginUserWithoutPassword(
|
|
'some@getunleash.io',
|
|
false, // autoCreateUser. Set to true if you want to create users on the fly.
|
|
);
|
|
|
|
// The user needs to be set on the current active session
|
|
req.session.user = user;
|
|
```
|
|
|
|
- [Read more about Securing Unleash v4](./securing-unleash.md)
|
|
- [Read more about RBAC](../../reference/rbac.md)
|
|
|
|
### 4. Legacy v2 routes removed {#4-legacy-v2-routes-removed}
|
|
|
|
Only relevant if you use the `enableLegacyRoutes` option.
|
|
|
|
In v2 you could query feature toggles on `/api/features`. This was deprecated in v4 and we introduced two different endpoints (`/api/admin/features` and `/api/client/features`) to be able to optimize performance and security. In v3 you could still enable the legacy routes via the `enableLegacyRoutes` option. This was removed in v4.
|
|
|
|
### 5. Unleash CLI has been removed {#5-unleash-cli-has-been-removed}
|
|
|
|
Unleash no longer ships with a binary that allows you to start Unleash directly from the command line. From v4 you need to either use Unleash via docker or programmatically.
|
|
|
|
Read more in our [getting started documentation](./getting-started.md)
|
|
|
|
## Upgrading from v2.x to v3.x {#upgrading-from-v2x-to-v3x}
|
|
|
|
The notable change introduced in Unleash v3.x is a strict separation of API paths for client requests and admin requests. This makes it easier to implement different authentication mechanisms for the admin UI and all unleash-clients. You can read more about [securing unleash](./securing-unleash.md).
|
|
|
|
The recommended approach is to first upgrade the `unleash-server` to v3 (which still supports v2 clients). After this is done, you should upgrade all your clients to v3.
|
|
|
|
After upgrading all your clients, you should consider turning off legacy routes, used by v2 clients. To do this, set the configuration option `enableLegacyRoutes` to `false` as described in the [page on configuring Unleash v3](./configuring-unleash-v3.md).
|
|
|
|
## Upgrading from v1.0 to v2.0 {#upgrading-from-v10-to-v20}
|
|
|
|
### Caveat 1: Not used db-migrate to migrate the Unleash database? {#caveat-1-not-used-db-migrate-to-migrate-the-unleash-database}
|
|
|
|
In FINN we used liquibase, for internal reasons, to migrate our database. Because unleash from version 2.0 migrates the database internally, with db-migrate, you need to make sure that all previous migrations for version 1 exist, so that Unleash does not try to create already existing tables.
|
|
|
|
#### How to check? {#how-to-check}
|
|
|
|
If you don't have a "migrations" table with _7 unique migrations_ you are affected by this.
|
|
|
|
#### How to fix? {#how-to-fix}
|
|
|
|
Before starting unleash version 2 you have to run the SQL located under `scripts/fix-migrations-version-1.sql`
|
|
|
|
### Caveat 2: databaseUrl (not database*Uri*) {#caveat-2-databaseurl-not-databaseuri}
|
|
|
|
Using Unleash as a library and injecting your own config? Then you should know that we changed the `databaseUri` config param name to **databaseUrl**. This is to make sure the param is aligned with the environment variable `DATABASE_URL` and avoid multiple names for the same config param.
|