Skip to main content

atlas-provider-django

Use Atlas with Django to manage your database schema as code. By connecting your Django models to Atlas, you can define and edit your schema directly in Python. Atlas will then automatically plan and apply database schema migrations for you, eliminating the need to write migrations manually.

Atlas brings automated CI/CD workflows to your database, along with built-in support for testing, linting, schema drift detection, and schema monitoring. It also allows you to extend Django with advanced database objects such as triggers, row-level security, and custom functions that are not supported natively.

Use-cases

  1. Declarative migrations - Use the Terraform-like atlas schema apply --env django command to apply your Django schema to the database.
  2. Automatic migration planning - Use atlas migrate diff --env django to automatically plan database schema changes and generate a migration from the current database version to the desired version defined by your Django schema.

Installation

Install Atlas for macOS or Linux by running:

curl -sSf https://atlasgo.sh | sh

See atlasgo.io for more installation options.

Install the provider by running:

pip install atlas-provider-django

Configuration

Add the provider to your Django project's INSTALLED_APPS in settings.py:

INSTALLED_APPS = [
    ...,
    'atlas_provider_django',
    ...
]

In your project directory, create a new file named atlas.hcl with the following contents:

data "external_schema" "django" {
  program = [
    "python",
    "manage.py",
    "atlas-provider-django",
    "--dialect", "mysql" // mariadb | postgresql | sqlite | mssql
    // if you want to only load a subset of your app models, you can specify the apps by adding
    // "--apps", "app1", "app2", "app3"
  ]
}

env "django" {
  src = data.external_schema.django.url
  dev = "docker://mysql/8/dev"
  migration {
    dir = "file://migrations"
  }
  format {
    migrate {
      diff = "{{ sql . \"  \" }}"
    }
  }
}

Usage

Inspect

You can use the atlas schema inspect command to visualize your Django schema in Atlas Cloud.

atlas schema inspect -w --env django --url env://src

inspect example

Apply

You can use the atlas schema apply command to plan and apply a migration of your database to your current Django schema. This works by inspecting the target database and comparing it to the Django Apps models and creating a migration plan. Atlas will prompt you to confirm the migration plan before applying it to the database.

atlas schema apply --env django -u "mysql://root:password@localhost:3306/mydb"

Where the -u flag accepts the URL to the target database.

Diff

Atlas supports a versioned migrations workflow, where each change to the database is versioned and recorded in a migration file. You can use the atlas migrate diff command to automatically generate a migration file that will migrate the database from its latest revision to the current Django schema.

atlas migrate diff --env django 

Supported Databases

The provider supports the following databases:

  • MySQL
  • MariaDB
  • PostgreSQL
  • SQLite
  • Microsoft SQL Server

Issues

Please report any issues or feature requests in the ariga/atlas repository.

License

This project is licensed under the Apache License 2.0.

Metadata

Release files for atlas-provider-django 0.2.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for atlas-provider-django 0.2.4
File Size Uploaded Provenance Actions
atlas_provider_django-0.2.4.tar.gz 9.6 kB Without provenance Details for atlas_provider_django-0.2.4.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for atlas-provider-django 0.2.4
File Interpreter ABI Platform Actions
atlas_provider_django-0.2.4-py3-none-any.whl Python 3 none any Details for atlas_provider_django-0.2.4-py3-none-any.whl

Total release size: 21.2 kB

Release files / atlas_provider_django-0.2.4.tar.gz

Download URL atlas_provider_django-0.2.4.tar.gz
Size 9.6 kB
Tags Source
SHA-256 checksum
How to use checksums
de33aa8c54782c81c1b2bdd6c565b97835a51cac02b2a7e4a8a1c7eb96b1e3bd
BLAKE2b-256 checksum
How to use checksums
9291ced8a924e26aecd124fb2cce61e8b173ea83c9631cbebe86a6bac38d174b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/2.1.3 CPython/3.13.1 Linux/6.11.0-1015-azure

Release files / atlas_provider_django-0.2.4-py3-none-any.whl

Download URL atlas_provider_django-0.2.4-py3-none-any.whl
Size 11.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9d7a5c10d43cd6279101c12713611433373d9b711702be5151d3f5d558b73913
BLAKE2b-256 checksum
How to use checksums
63609be47b430d35417e381890773f7cedb3f564ecd17702ba2d88d18e73792f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/2.1.3 CPython/3.13.1 Linux/6.11.0-1015-azure

Security for atlas-provider-django 0.2.4

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page