Forest admin cli reporting wrong environment

Help me!
1

Hi,
we’ve recently upgraded and moved our production infrastructure environment. We’ve upgraded forest-express-sequelize to version 8.5.3 and after that we pointed Forest to the new production url.

This is the information that I get about my local environment

forest environments:get <redacted>
ENVIRONMENT 
 url                http://localhost:3310                                             
 active             true                                                              
 type               development                                                       
 liana              forest-express-sequelize                                          
 version            8.5.3

but this is what I get from our production environment

ENVIRONMENT 
 name               Production                                                        
 url                <redacted>
 active             true                                                              
 type               production                                                        
 liana              forest-express-sequelize                                          
 version            7.11.3

The url matches our new url, but the forest-express-sequelize version is wrong. The server is running 8.5.3 (confirmed also by running npm list forest-express-sequelize).

Observed behavior

Not sure if the above is the cause, but we get all kinds of problems after this update.

  • the timestamp query parameter is not sent anymore when invoking smart actions, breaking the application (however it works correctly in the local environment)
  • the ui is a little bit different than before (renamed columns, naming differences, columns in different positions), even if we haven’t pushed any visual change as part of this upgrade.

We’ve also tried to change the layout locally, push it in our staging environment (which matches the local environment) and then deploy to production, but we get this error:

× Source and destination environments must have the same schema. Please check your environments code is synchronized.

However the .forestadmin-schema.json is identical in all 3 environments.

Context

  • Project name: Content Admin
  • Team name: Content Team
  • Environment name: Production
  • Agent type & version: Sequelize, 8.5.3 running on Node 16
2

Hey @mauricius, and welcome to our community :wave:

On my end, your production environment is still considerer as 7.11.3.
Can you confirm that on your production server, the .forestadmin-schema.json contains the correct 8.5.3 version (In the meta section) ?

Thanks in advance :pray:

1 Like
4

Yes, I can confirm it.

"meta": {
    "liana": "forest-express-sequelize",
    "liana_version": "8.5.3",
    "stack": {
      "database_type": "mysql",
      "engine": "nodejs",
      "engine_version": "14.15.3",
      "orm_version": "6.17.0"
    }
  }
1 Like
5

Weird … I cannot see your schema as being updated on our end, still using 7.11.3

Do you eventually use the FOREST_DISABLE_AUTO_SCHEMA_APPLY=true variable? Each server (re)start should send the .forestadmin-schema.json to our server, however, the last one I can see still refers to the 7.11.3 version.

In the meantime, I’ll check our logs to see if I’m able to spot anything :pray:

6

No I set that variable only locally, during tests. In production I can confirm that the only FOREST_ variables used are FOREST_AUTH_SECRET and FOREST_ENV_SECRET.

BTW we also have a staging environment that runs the same stack and the forest cli correctly reports that is running 8.5.3

ENVIRONMENT 
 name               Staging                                                           
 url                <redacted>
 active             true                                                              
 type               remote                                                            
 liana              forest-express-sequelize                                          
 version            8.5.3
9

Solved the problem privately. Long story short, the old environment was still advertising the old version of the .forestadmin-schema.json file.

2 Likes