sourcegraph/cmd/msp-example
Robert Lin ec5b645b69
cmd/msp-example: remove gorm (#62110)
gorm is a heavy-ish dependency and not _actually_ used anywhere in the monorepo - I mostly added this to ensure we had comprehensive test environment coverage for SAMS and SSC use cases, which do use gorm in separate repositories.

Both of the above services now have their own long-lived dev environments - we no longer need such a comprehensive example, and a simple ping and query will do for msp-example.

## Test plan

Add `sg.config.overwrite.yaml` to override the database connection with local dev:

```yaml
  msp-example:
    env:
      STATELESS_MODE: false
      PGDSN: 'user=sourcegraph password=sourcegraph database=sourcegraph'
```

Start msp-example:

```sh
sg run msp-example
```

Observe logs reach the point where the Postgres is connected to successfully (then fails due to other things, but that is okay):

```
[    msp-example] INFO service example/example.go:47 starting service
[    msp-example] INFO service example/example.go:53 postgresql connection success
```
2024-04-23 20:00:10 +00:00
..
internal/example cmd/msp-example: remove gorm (#62110) 2024-04-23 20:00:10 +00:00
BUILD.bazel Publish sourcegraph-base image (#62002) 2024-04-19 14:44:06 +01:00
image_test.yaml dev/msp: add CloudSQL integration (#58420) 2023-11-22 15:32:53 -08:00
main.go msp/runtime: export contract and helpers for direct usage (#61488) 2024-04-04 11:05:51 +00:00
README.md bazel: use transitions to apply cross-compile platform automatically to oci_image (#60569) 2024-02-20 13:57:56 +00:00

msp-example

This service is an example service testing and demonstrating how to build Managed Services Platform services: go/msp

Pushing a new version

bazel run //cmd/msp-example:candidate_push --stamp -- --tag insiders --repository us.gcr.io/sourcegraph-dev/msp-example