| commit | 1128286c2720c816c697a4a841fcf16e38e695b8 | [log] [tgz] |
|---|---|---|
| author | Jonathan Amsterdam <jba@google.com> | Tue Sep 10 05:04:43 2019 -0400 |
| committer | Julie Qiu <julie@golang.org> | Fri Mar 27 16:46:43 2020 -0400 |
| tree | febbe78d1903a2fbd1cc28e3c75ba44ed75c917e | |
| parent | a0b57d4686c6f3553b689b97042aa223df87503d [diff] |
cmd/prober: a prober for the discovery site This initial version isn't exporting any metrics yet (that is the next step) but it has a status page you can view at Also: fiddle with the auth package API and move the package up a level so the prober can use it. See b/133164583. Change-Id: Id6428750fef2f823a5d1cc2a34534c4774d29a1d Reviewed-on: https://team-review.git.corp.google.com/c/golang/discovery/+/549835 Reviewed-by: Robert Findley <rfindley@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.