mirror of https://github.com/peeringdb/peeringdb.git synced 2024-05-11 05:55:09 +00:00

Files

Matt Griswold 5147028bee clean up / format / poetry (#1000 )

* stub in poetry for pipenv

* re-add tester image

* add pre-commit / formatting

* fix ghactions

* revert test data whitespace, exclude tests/data

* revert ws

* decruft, rm tox/pipenv

* install dev packages for base image

* add lgtm config to force to py3

2021-07-10 10:12:35 -05:00

679 B

Raw Blame History

Commands

Can be run from prod0

undelete

First find out the version id when the object was deleted

python manage.py pdb_reversion_inspect <reftag> <id>

VERSION: 7 (392112) - 2018-12-24T07:13:49.612Z - User: johnsmith
status: 'ok' => 'deleted'

You want the number inside the brackets (in this case 392112)

Then run the undelete command

python manage.py pdb_undelete <reftag> <id> <version id>

This will show you everthing that will be undeleted, it will run in pretend mode, nothing is committed yet.

After reviewing, run the command again with the --commit flag

python manage.py pdb_undelete <reftag> <id> <version id> --commit

679 B Raw Blame History

Commands

undelete

679 B

Raw Blame History