2 posts tagged with "terraform"

With Atlas, we advocate for treating migration directories as deployment artifacts resulting from a structured build process. The preferred approach is to push migration directories to the Atlas Schema Registry. In addition to its role as a migration directory storage, the Schema Registry provides a tight integration with the Atlas CLI and the Atlas Cloud UI, allowing you to deploy migrations, visualize schemas over time, review deployment logs and errors, and more.

However, some users prefer to store their migration directories in S3, typically due to internal policies or requirements.

Terraform can write resource arguments into state and saved plans. HashiCorp's Terraform state documentation warns that state files can expose stored secrets. The sensitive flag redacts CLI and UI output, but Terraform can still record the value in state.

With the atlas_schema resource, Terraform can pass connection metadata while Atlas resolves the credential when it evaluates atlas.hcl.