Review all timestamps (db_state_at and others), clarify the meanings
Goal
db_state_at
corresponds
-
UI @dmius -
the platform reads the value from DB Lab API @dmius -
at snapshotting time on DB Lab instance, we need to determine db_state_at
and store it somewhere -
dblab API to provide the data @anatolystansler -
review texts
TODO / How to implement
Review all timestamps, clarify the meanings. The time of the latest available database state seems to be not correct (too fresh). UI expects db_state_at, if there is no such field, we show "unknown".
The logic for snapshots list exposure is needed. If a corresponding API call is made, we need to scan all existing snapshots, choose the proper ones according to some mask (should it be configurable?), and reply with list to the API call. Don't worry about long lists. Instead, consider providing a warning if the list exceeds 50 items ("The list of available snapshots exceeds 50, clean up some old ones not to waste of disk space and avoid potential performance degradation").
Acceptance criteria
Edited by Nikolay Samokhvalov