| commit | 3a1c21670c69e77e69cbcad7d2f557383d2634c5 | [log] [tgz] |
|---|---|---|
| author | Jonathan Amsterdam <jba@google.com> | Fri Dec 20 11:50:25 2019 -0500 |
| committer | Julie Qiu <julie@golang.org> | Fri Mar 27 16:46:50 2020 -0400 |
| tree | 3a405023c475e73553bfa1a2da49096bbc3e6ccf | |
| parent | a72c2ab9ef763fea88a865dfb39feb6df9829580 [diff] |
internal/etl: display meaning of codes on status page We have enough status codes for ETL fetches that it's hard to understand the table on the status page. Add a description for each code. Change-Id: I45c225dd032a9da80d24891a3eafe523db3c8ee5 Reviewed-on: https://team-review.git.corp.google.com/c/golang/discovery/+/623924 Reviewed-by: Julie Qiu <julieqiu@google.com>
Migrations are managed with the golang-migrate/migrate CLI tool.
To run all the migrations:
migrate -source file:migrations -database "postgres://localhost:5432/discovery-database?sslmode=disable" up
To create a new migration:
migrate create -ext sql -dir migrations -seq <title>
This creates two empty files in /migrations:
{version}_{title}.up.sql
{version}_{title}.down.sql
The two migration files are used to migrate “up” to the specified version from the previous version, and to migrate “down” to the previous version. See golang-migrate/migrate/MIGRATIONS.md for details.