How to detect schema drift in CI and ensure the migration directory is up to date with the desired schema state - ORM, HCL, SQL, or any other schema definition?

A .env file is a simple text file used to store environment variables for applications. It helps developers manage configuration settings, such as database credentials, API keys, and other sensitive information, without hardcoding them into the source code. By using a .env file, developers can keep their codebase clean, secure, and easily configurable across different environments.

For developers who want to use .env files with Atlas, there are two ways users can do so through the standard Atlas HCL configuration file:

PostGIS is a spatial database extension for PostgreSQL. It adds support for geometric objects, enabling the processing of spatial data like points, lines, and polygons. After installing PostGIS, the GEOMETRY data type can be used to define tables that capture geo-spatial data, for example:

How can I install Atlas, and why is go install no longer supported?

Why does atlas migrate diff fail with a "connected database is not clean" error after running atlas migrate apply?

Question​

How to generate an SQL schema file from an existing migrations directory to quickly set up a database for integration tests?

How do I fix the ModifySchema is not allowed when migration plan is scoped to one schema error?

After upgrading Atlas, you might encounter an error stating "Feature X is no longer supported by this release."

For example:

Error: data.external_schema is no longer supported by this release.

This occurs when you install the community version of Atlas, which lacks some features available only in non-community builds.

To include a PostgreSQL extension in your schema, there are a few configurations to be made to ensure the extension is properly applied.

How to use a database URL that contains a password with special characters such as @ or #?