DATA_STEPS_BACKUP_DECLINED
A command would change data an earlier Nextly release stored, and its backup question was answered no.
Cause
A command would change data an earlier Nextly release stored, and its backup question was answered no.
nextly migrate, nextly db:sync and nextly i18n:convert-zoned-dates rewrite values an earlier release stored, in place, so each asks whether the database is backed up before it changes anything. At the prompt the answer was no, so nothing was changed.
The one exception is a run that could not see the work before it changed the schema: nextly migrate --step, or work on a table the migrations or the sync create. That run asks after its schema changes have applied. A no then leaves those changes applied and the stored data as it was, and the message says so: the database has this release's schema, and the data steps have not run.
Fix
- Back up the database.
- Run the command again and answer yes, or pass
--backup-confirmed. Where the schema changes had applied, the second run has nothing left to migrate or sync and takes only the data steps.
Example
✗ The data an earlier Nextly release stored was left as it is (hash passwords stored before this release: 3): the backup question was answered no.
Why: The command rewrites stored values in place, so it asks for a backup first, and the answer was no. Nothing was changed.
Next: Back up the database, then run `nextly migrate` again and answer yes, or pass `--backup-confirmed`.
Docs: https://nextlyhq.com/docs/cli/errors/data-steps-backup-declined (DATA_STEPS_BACKUP_DECLINED)