Feature(s) impacted
Not sure if this impacts anything, as all models appear fine when we deploy the models/
output directory to production.
Observed behavior
We we’ve been running forest schema:update
in CI for a long while, and recently noticed that the .forestadmin-schema.json
file is very old and out of date. However, the models/ dir does contain the updated schema for our DB.
Expected behavior
I don’t know what is the desired behaviour, but it should be either:
- the file is needed - and then the file should be updated when running
schema:update
- the file is not needed - we should update docs about this fact
Failure Logs
N/A
Context
- Project name: …
- Team name: …
- Environment name: …
- Database type: PostgreSQL
- Recent changes made on your end if any: …
And, if you are self-hosting your agent:
- Agent technology: nodejs
- Agent (forest package) name & version (from your .lock file):
forest-cli": "^5.2.2"