DevOps & Infrastructure

Atlas Spanner

Google Cloud Spanner specifics for Atlas: the extended build and login, URLs and Application Default Credentials, GoogleSQL and PostgreSQL dialects, the emulator dev database and what it lacks, `-- atlas:txmode none` in every migration file, partial failures and long-running schema changes (index backfills, validations, Google's batch limits), what Spanner cannot change in place (primary keys, interleaving, column types, renames), objects Atlas leaves out or plans wrongly (identity columns, NOT ENFORCED foreign keys, interleaved indexes, change streams, database options), hotspot-free keys and bit-reversed sequences, named schemas, roles and grants, migration tests in place of schema tests, mutation limits and batched backfills, and custom lint rules. Use with the atlas skill whenever Atlas manages a Spanner database.

Publisher / source
ariga/atlas (found on GitHub top repositories)
Upstream record
ariga/atlas
Version
Version 1
Published
Publication review
Approved for publication
Content fingerprint
1915bf8952ca136ae1a7b4d764dc3f541aa775d857837f366a7e488946d0b6d5