From 1ca764a9456512a3dbdcbf83e4a337cdfc982dbe Mon Sep 17 00:00:00 2001 From: Rob Austein Date: Sun, 14 Sep 2014 00:28:56 +0000 Subject: 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 --- rpki/irdb/models.py | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'rpki/irdb') 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 -- cgit v1.2.3