Skip to main content

Detect backward incompatible migrations for your django project

Project description

Detect backward incompatible migrations for your django project. It will save you time by making sure migrations will not break anything.

https://travis-ci.org/3YOURMIND/django-migration-linter.svg?branch=master https://img.shields.io/pypi/v/django-migration-linter.svg https://img.shields.io/github/license/3yourmind/django-migration-linter.svg https://img.shields.io/badge/PR-welcome-green.svg https://img.shields.io/badge/3YOURMIND-Hiring-brightgreen.svg https://img.shields.io/github/stars/3YOURMIND/django-migration-linter.svg?style=social&label=Stars

Installation

pip install django-migration-linter

Usage

Add the migration linter your INSTALLED_APPS:

INSTALLED_APPS = [
    ...,
    "django_migration_linter",
    ...,
]

python manage.py lintmigrations [GIT_COMMIT_ID] [--ignore-name-contains=IGNORE_NAME_CONTAINS] [--include-apps INCLUDE_APPS [INCLUDE_APPS ...] | --exclude-apps EXCLUDE_APPS [EXCLUDE_APPS ...]]

Parameter

Description

DJANGO_PROJECT_FOLDER

An absolute or relative path to the django project.

GIT_COMMIT_ID

If specified, only migrations since this commit will be taken into account. If not specified, all migrations will be linted.

--ignore-name-contains IGNORE_NAME_CONTAINS

Ignore migrations containing this name.

--ignore-name IGNORE_NAME [IGNORE_NAME ...]

Ignore migrations with exactly one of these names.

--include-apps INCLUDE_APPS [INCLUDE_APPS ...]

Check only migrations that are in the specified django apps.

--exclude-apps EXCLUDE_APPS [EXCLUDE_APPS ...]

Ignore migrations that are in the specified django apps.

--verbose or -v

Print more information during execution.

--database DATABASE

Specify the database for which to generate the SQL. Defaults to default.

--cache-path PATH

specify a directory that should be used to store cache-files in.

--no-cache

Don’t use a cache.

Examples

3YOURMIND is running the linter on every build getting pushed through CI. That enables to be sure that the migrations will allow A/B testing, Blue/Green deployment and they won’t break your development environment. As every reasonable tool, a non-zero error code means that at least one invalid migration has been found.

Backward incompatible migrations

The linter analyses your migrations and checks the SQL for:

  • Added NOT NULL columns, which don’t have a DEFAULT value

  • Dropping columns

  • Renaming columns

  • Renaming tables

  • Altering columns (which can be backward compatible and potentially ignored)

Those are the most important and frequent backward incompatible migrations. We are happy to add more if you can specify them to us.

Ignoring migrations

You can also ignore migrations by adding this to your migrations:

import django_migration_linter as linter
# ...

    operations = [
        linter.IgnoreMigration(),
        # ...
    ]
# ...

Cache

By default, the linter uses a cache to prevent linting the same migration multiple times. The default location of the cache on Linux is /home/<username>/.cache/django-migration-linter/<version>/<ldjango-project>_<database_name>.pickle.

Since the linter uses hashes of the file’s content, modifying a migration file will re-run the linter on that migration. If you want to run the linter without cache, use the flag --no-cache. If you want to invalidate the cache, delete the cache folder. The cache folder can also be defined manually through the --cache-path option.

Tests

The easiest way to run the tests is to invoke tox.

You will need to install the test requirements, which can be found in the setup.py file. A good way to get started is to install the development version of the linter by doing pip install -e .[test].

To be able to fully test the linter, you will need both MySQL and PostgreSQL databases running. You can either tweak the tests/test_project/settings.py file to get your DB settings right, or to have databases and users corresponding to the default Travis users.

Contributing

First, thank you very much if you want to contribute to the project. Please base your work on the master branch and also target this branch in your pull request.

Publishing the package

A small note on how the linter is usually published to PyPi:

  • python setup.py check --restructuredtext

  • python3 setup.py sdist bdist_wheel --universal

  • twine upload dist/django_migration_linter-X.Y.Z-py2.py3-none-any.whl dist/django-migration-linter-X.Y.Z.tar.gz

Blog post

Keeping Django database migrations backward compatible

License

django-migration-linter is released under the Apache 2.0 License.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

django-migration-linter-1.1.0.tar.gz (23.6 kB view details)

Uploaded Source

Built Distribution

django_migration_linter-1.1.0-py2.py3-none-any.whl (55.9 kB view details)

Uploaded Python 2 Python 3

File details

Details for the file django-migration-linter-1.1.0.tar.gz.

File metadata

  • Download URL: django-migration-linter-1.1.0.tar.gz
  • Upload date:
  • Size: 23.6 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.6.3 requests-toolbelt/0.8.0 tqdm/4.29.1 CPython/3.6.7

File hashes

Hashes for django-migration-linter-1.1.0.tar.gz
Algorithm Hash digest
SHA256 53522ab0ee63500ebbaca6c62f04ae3285c44e5bc23c1ab399df78db42b2f933
MD5 aeecbc4be94d5bcd434ae250a4fe0004
BLAKE2b-256 b82ef15187cdbb283afc860333ffcd72fe5f24d536467c062e49eba49248b8a6

See more details on using hashes here.

File details

Details for the file django_migration_linter-1.1.0-py2.py3-none-any.whl.

File metadata

  • Download URL: django_migration_linter-1.1.0-py2.py3-none-any.whl
  • Upload date:
  • Size: 55.9 kB
  • Tags: Python 2, Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.6.3 requests-toolbelt/0.8.0 tqdm/4.29.1 CPython/3.6.7

File hashes

Hashes for django_migration_linter-1.1.0-py2.py3-none-any.whl
Algorithm Hash digest
SHA256 b658c57757c1f8356c9626dd59c3877b5ab7604ca29e9ceac4f585888e45e916
MD5 7c5541e3c154c851c39eeda3671dbb4c
BLAKE2b-256 c5e86d7bdd88ca076c65f4c0bbab9c5aa7ad5c8464310e074947927bb1bb4dcc

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page