Wrong alert or did I miss something?

Help me!
1

Observed behavior

After updating from 7.9.x to 8.7.x, I still have this alert message

image

Expected behavior

No more alert message

Context

  • Project name: lereacteur-admin
  • Environment name: Development
  • Agent (forest package) name & version: "forest-express-mongoose": "^8.7.9"
  • Database type: MongoDB
  • Recent changes made on your end if any: Update from 7 to 8.
2

Hello @XavierColombel,

From what I can see on our side, your environments are still on 7.9.2, after updating to 8.7.X, do you confirm that your .forestadmin-schema.json file do have “liana_version” set to the proper version ?

  • If the file contains the older version this means that your schema generation is disabled, this is the case when NODE_ENV=production (see documentation)
  • if the file has been generated properly but for some reason hasn’t been pushed to our backend, you can force it by executing the command forest schema:apply (doc)

Best regards,

3

Here is my infos from forestadmin-schema.json (I talk about dev env) :

"liana": "forest-express-mongoose",
"liana_version": "8.7.9",
"stack": {
"database_type": "MongoDB",
"engine": "nodejs",
"engine_version": "16.17.0",
"orm_version": "5.8.13"

I don’t have a NODE_ENV params in .env file.

I don’t especially want to push my file to my backend, because the migration isn’t done yet. So, if I use forest schema:apply, it might broke anything in production (actually, it’s still on 7.9 version), right ?

4

your liana_version has been updated so no issues on this side.
It should send the new schema automatically when the agent is starting, do you have any log when restarting your agent in development ?

I don’t especially want to push my file to my backend, because the migration isn’t done yet. So, if I use forest schema:apply , it might broke anything in production (actually, it’s still on 7.9 version), right ?

The command forest schema:apply does not push your schema to your production environment. All it does is fetch the .forestadmin-schema.json and send it to us via the environment secret defined in your .env, you should execute this command in your development project if you have no success when restarting the agent (and no log).

it might broke anything in production (actually, it’s still on 7.9 version), right ?

Yes your production is still market as 7.9.2

Edit: While looking just now I can see that your development environment has been updated to the proper version, the schema must have been sent on the agent restart

5

I type the forest schema:apply and I had the update. But, I have to no it manually each time. Btw, it’s working.