It would be great if you could plug in other configuration frontends. I'd love to be able to just define a proto and have this manage database schemas for me.
Atlas – A Database Toolkit
11–14 of 14 posts
Re: Atlas – A Database Toolkit
#12Atlas is quite nice. I recently started using it in a typescript/node.js project (which was using liquibase before) and I find the DX to be great. Primary additional feature I wish it had is support for manual migrations in addition to declarative hcl. So it would be great if I could have a unified changelog or migration list where some of the migrations were autogenerated from the diff in hcl and others were manuall…
declarative hcl HCL? Edit: Found it. “HashiCorp Configuration Language, a computer configuration language, used by Terraform.” It’s surprisingly hard to Google for.
Everything is hard to google for engineering these days.
Re: Atlas – A Database Toolkit
#13Going through the readme and the homepage still left me asking "What exactly does it do?". Going through the readme, their home page, and this blog post ( https://blog.ariga.io/meet-atlas-cli/ ), here's a tldr; It's terraform, but for database. - It allows defining SQL database schema in HCL (terraform's DSL) for now. - It can inspect a database and create the HCL for it. - It can do database migrations similar to te…
Hey bitspook! One of Atlas’s creators here. Thanks for sharing this! You describe the existing state well. Atlas can currently be used to perform what we call declarative database migrations. This is great for many use cases. But it will not do for others, for a few reasons . First, there are many ways to get from point A to point B. The classic example is a table rename. To get from the existing to the desired state…
this sounds interesting! can you please do a comparison matrix with flyway and also think if you can implement its features?
The iterative approach helps massively
Re: Atlas – A Database Toolkit
#14It would be great if you could plug in other configuration frontends. I'd love to be able to just define a proto and have this manage database schemas for me.
Hey gravypod!
Thanks for writing. Indeed we built the schemaspec implementation so that it’s definitely possible to use other syntaxes to define schemas. HCL was chosen for various reasons to be first but we are planning on supporting others