# Upgrade liana v9 sequelize

**URL:** <https://community.forestadmin.com/t/upgrade-liana-v9-sequelize/6316>\
**Category:** Help me!\
**Created:** [May 18, 2023, 8:58pm UTC](https://community.forestadmin.com/t/upgrade-liana-v9-sequelize/6316 "2023-05-18T20:58:05Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![felipe.prservicos](https://avatars.discourse-cdn.com/v4/letter/f/a6a055/32.png) [@felipe.prservicos](https://community.forestadmin.com/u/felipe.prservicos)\
**Post date:** [May 18, 2023, 8:58pm UTC](https://community.forestadmin.com/t/upgrade-liana-v9-sequelize/6316/1 "2023-05-18T20:58:05Z")

</div>

## Feature(s) impacted

I can’t upgrade forest-express-sequelize from version 8.5.14 to 9.x.x versions. When I do that I get the following error:

## Failure Logs

```javascript
[forest] 🌳🌳🌳 Unexpected error: Invalid value "undefined" for header "forest-secret-key"
{
  "code": "ERR_HTTP_INVALID_HEADER_VALUE",
  "stack": "TypeError: Invalid value \"undefined\" for header \"forest-secret-key\"\n at ClientRequest.setHeader (node:_http_outgoing:579:3)\n at Request.request (/Users/x308449/apps/monofolio/common/temp/node_modules/.pnpm/superagent@7.1.5/node_modules/superagent/src/node/index.js:850:39)\n at Request.end (/Users/x308449/apps/monofolio/common/temp/node_modules/.pnpm/superagent@7.1.5/node_modules/superagent/src/node/index.js:972:8)\n at /Users/x308449/apps/monofolio/common/temp/node_modules/.pnpm/superagent@7.1.5/node_modules/superagent/src/request-base.js:285:12\n at new Promise (<anonymous>)\n at RequestBase.then (/Users/x308449/apps/monofolio/common/temp/node_modules/.pnpm/superagent@7.1.5/node_modules/superagent/src/request-base.js:267:31)"
}

```

## Context

- Project name: Passfolio
- Team name: Developers
- Environment name: Sandbox and Dev
- Agent (forest package) name & version: forest-express-sequelize@9.0.0

---

<div class="post-metadata">

**Author:** ![Alban\_Bertolini](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/alban_bertolini/32/1077_2.png) [@Alban\_Bertolini](https://community.forestadmin.com/u/Alban_Bertolini)\
**Post date:** [May 19, 2023, 7:07am UTC](https://community.forestadmin.com/t/upgrade-liana-v9-sequelize/6316/2 "2023-05-19T07:07:36Z")

</div>

Have,  
Have you assigned the value for your FOREST\_ENV\_SECRET variable in your .env file or in your environment variables?  
Did you follow this [tutoriel](https://docs.forestadmin.com/documentation/how-tos/maintain/upgrade-notes-sql-mongodb/upgrade-to-v8)?

---

<div class="post-metadata">

**Author:** ![felipe.prservicos](https://avatars.discourse-cdn.com/v4/letter/f/a6a055/32.png) [@felipe.prservicos](https://community.forestadmin.com/u/felipe.prservicos)\
**Post date:** [May 19, 2023, 1:40pm UTC](https://community.forestadmin.com/t/upgrade-liana-v9-sequelize/6316/3 "2023-05-19T13:40:12Z")

</div>

You are correct, the problem is that there is a breaking change from 8.5.14 to 9.0.0 which is not listed in your docs. It doesn’t matter if you call `Liana.init` passing the `envSecret`, at some point you guys are reading from `process.env.FOREST_ENV_SECRET` which doesn’t make any sense to me. Any idea why you changed this? I can’t set `process.env.FOREST_ENV_SECRET`, we get all your secrets at runtime using Google KMS…

```javascript
await Liana.init({
  configDir: __dirname + '/../../forest',
  schemaDir: __dirname + '/../../..',
  // envSecret is loaded at runtime from Google KMS, not available at process.env.FOREST_ENV_SECRET
  envSecret: kms.settings.FOREST_ENV_SECRET,
  authSecret: kms.settings.FOREST_AUTH_SECRET,
  connections: db.connections,
  objectMapping: db.objectMapping
})

```

---

<div class="post-metadata">

**Author:** ![felipe.prservicos](https://avatars.discourse-cdn.com/v4/letter/f/a6a055/32.png) [@felipe.prservicos](https://community.forestadmin.com/u/felipe.prservicos)\
**Post date:** [May 19, 2023, 1:56pm UTC](https://community.forestadmin.com/t/upgrade-liana-v9-sequelize/6316/4 "2023-05-19T13:56:35Z")

</div>

Problem is here:

> <https://github.com/ForestAdmin/forest-express/blob/fe49b57222ff1756a65c86ac2d0e09814bd8c56c/src/context/build-services.js#L9>

Wrong:

```ts
envSecret: env.FOREST_ENV_SECRET,

```

Right

```ts
envSecret: configStore.lianaOptions.envSecret || env.FOREST_ENV_SECRET,

```

---

<div class="post-metadata">

**Author:** ![Alban\_Bertolini](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/alban_bertolini/32/1077_2.png) [@Alban\_Bertolini](https://community.forestadmin.com/u/Alban_Bertolini)\
**Post date:** [May 20, 2023, 8:37pm UTC](https://community.forestadmin.com/t/upgrade-liana-v9-sequelize/6316/5 "2023-05-20T20:37:56Z")

</div>

I will push your feedback as a regression and it will be fixed.  
A workaround is to set the env variables before the liana init.

```javascript
process.env.envSecret = kms.settings.FOREST_ENV_SECRET;
process.env.authSecret = kms.settings.FOREST_AUTH_SECRET;

```

---

<div class="post-metadata">

**Author:** ![felipe.prservicos](https://avatars.discourse-cdn.com/v4/letter/f/a6a055/32.png) [@felipe.prservicos](https://community.forestadmin.com/u/felipe.prservicos)\
**Post date:** [May 22, 2023, 7:23pm UTC](https://community.forestadmin.com/t/upgrade-liana-v9-sequelize/6316/6 "2023-05-22T19:23:24Z")

</div>

Ok, that solves the problem for now.

---

<div class="post-metadata">

**Author:** ![morganperre](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/morganperre/32/1296_2.png) [@morganperre](https://community.forestadmin.com/u/morganperre)\
**Post date:** [May 24, 2023, 7:25am UTC](https://community.forestadmin.com/t/upgrade-liana-v9-sequelize/6316/7 "2023-05-24T07:25:23Z")

</div>

Hello @felipe.prservicos,

We’ve just released a new version of [forest-express-sequelize](https://www.npmjs.com/package/forest-express-sequelize) 🎉

Could you update to the latest version and remove the “monkey patch”?

Let us know if it works for you. 🙏

Kind regards,  
Morgan