aboutsummaryrefslogtreecommitdiff
path: root/rpki/irdb/models.py
diff options
context:
space:
mode:
authorRob Austein <sra@hactrn.net>2014-09-14 00:28:56 +0000
committerRob Austein <sra@hactrn.net>2014-09-14 00:28:56 +0000
commit1ca764a9456512a3dbdcbf83e4a337cdfc982dbe (patch)
tree41652de28b3bf53f4aba4dfac42ca9c7c305e4fb /rpki/irdb/models.py
parent773d3c3d01f39b1cedb7506ee7c1c3ceed91a17d (diff)
Start backing out all the old settings.configure() calls, which were
indeed masking the new migration stuff. yamltest now runs migrations as part of setting up test CAs; still need to decide whether running migrations in production is something that should be handled explicitly via rpki-manage or should be bundled into rpki-sql-setup. Old settings.configure() code still present as a trail of breadcrumbs to follow when backing out the rest of the tortuous startup sequence required by the old way of doing things. svn path=/branches/tk713/; revision=5950
Diffstat (limited to 'rpki/irdb/models.py')
-rw-r--r--rpki/irdb/models.py5
1 files changed, 5 insertions, 0 deletions
diff --git a/rpki/irdb/models.py b/rpki/irdb/models.py
index 2db86ba8..f89cebd4 100644
--- a/rpki/irdb/models.py
+++ b/rpki/irdb/models.py
@@ -81,6 +81,11 @@ class SignedReferralField(DERField):
description = "CMS signed object containing XML"
rpki_type = rpki.x509.SignedReferral
+# Alias to keep old rpki.gui migrations happy. Would generating a new
+# schema migration for rpki.gui remove the need, or do we have to
+# preserve every old field class we've ever used forever? Dunno.
+
+RSAKeyField = KeyField
# Introspection rules for Django South