Description
This issue is to keep a log of each time the server was upgraded. Users should have easy access to this history. We have discussed a few ideas for implementation:
- Manually write a database migration for each release. The migration would insert a row into the
auditstable indicating that the server has been upgraded. - Autogenerate a migration for each release. For separate reasons, we've been discussing writing a script that we would run before each release. Maybe that script could be what writes the migration for each release.
- Log server upgrade on server start
a. When we generate versions.txt?
b. Backend has access to the version of Central it's running via theSENTRY_TAGSenvironment variable (it's a JSON string; I think theversion.centralproperty is the one we want). Maybe Backend could compare the current version to what's already in the audit log. If they differ, it could log the current version.- Maybe this could be done in lib/bin/run-server.js.
- Alternatively, maybe it could be done in its own script. start-odk.sh could run that script after running lib/bin/run-migrations.js.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status