2bf70a10a2
In these instances, we take the migrations to be the "official" version - since they're stricter in almost all cases - updating the models to suit. This change highlights a slight issue in our use of a config option in our database schema, which we shouldn't really do. A TODO is left to address this later. We can also remove a now-unnecessary TODO from our initial migration related to the same issue: we have our own tooling for migrations that *does* load and register config options so there is no longer an issue here. Change-Id: I906cb8f7b76833c880a40c1aa0584fe7ab93cb7a Signed-off-by: Stephen Finucane <sfinucan@redhat.com> |
||
|---|---|---|
| .. | ||
| backends | ||
| providers | ||
| __init__.py | ||
| core.py | ||
| provider.py | ||
| schema.py | ||