Atlas (Issue #6): Schema change management for platform teams and more
Hi everyone!
Welcome to the sixth edition of our newsletter, where we periodically share updates and fresh content about everything Atlas.
Here’s what you can find in this edition:
Learn how platform teams can build schema change management into their platform.
See how to manage database schemas with Terraform in plain SQL in this new video!
Read about two useful new analyzers and about cloud linting configuration in this announcement.
Dive deep into preventing destructive changes to your database and troubleshooting migration failures.
Happy weekend,
Ariel and Rotem
P.S. Have you joined our Discord server? Join us and the rest of the community for Atlas-related discussions and help
Schema change management for platform teams
Schema change management refers to the collection of tools and processes that support the evolution of an application’s data model and the ways in which it is stored in databases. In this post, we review how platform teams can integrate it into their platforms.
Manage database schemas with Terraform in plain SQL
Read about two improvements to the developer experience of working with the Atlas Provider at the v0.5.0 of the Atlas Terraform Provider.
Support for the
docker://
driver for dev-databases.Support for defining the desired state of your database schema in plain SQL (and any other schema loader supported by Atlas).
Continuous Integration for databases
Read our latest blog posts about CI features supported by Atlas:
Preventing breaking changes to your database with Atlas
Learn what breaking changes are and how Atlas can help you prevent breaking schema changes from impacting your application.
Troubleshooting schema migration issues with Atlas
Explore the common causes of migration failures and reads about how Atlas can help you quickly recover from such failures and easily get back on track.
Enforcing naming conventions and concurrent index creation
Learn about new analyzers recently added to Atlas’s
lint
command and how to configure linting policies in Atlas Cloud.
More guides
Read these guides to learn more about the continuous delivery of database schema changes:
Provisioning schemas (named databases) with Terraform using Atlas
When preparing the infrastructure for the deployment of applications, IaC practitioners need to ensure the required schemas (named databases) exist on the database instance in which tables and other database resources will be created. Learn how to use Terraform for this instead of manually running:
CREATE SCHEMA myapp;
Deploying schema migrations to Google CloudSQL using Atlas and GitHub Actions
In this guide, we demonstrate how to handle database schema changes when working with Cloud SQL. We cover configuring Cloud SQL Auth Proxy to securely connect to your database from within GitHub Actions to apply schema changes.
Wrapping up
Thanks for reading this edition of the Atlas newsletter! If you have suggestions or requests for Atlas or this newsletter, feel free to drop us a line on Discord, Twitter, or GitHub