grafana/pkg/services/ngalert/api/tooling
2022-05-18 13:52:30 -05:00
..
cmd/clean-swagger Fix/ngalert generation (#33172) 2021-04-20 13:12:32 -04:00
definitions Indicate whether templates are provisioned (#49025) 2022-05-18 13:52:30 -05:00
swagger-codegen/templates Alerting: Provisioning API - Notification Policies (#46755) 2022-04-05 16:48:51 -05:00
.gitignore Alerting: Unify Swagger/OpenAPI generation tooling (#46928) 2022-03-31 09:34:46 +02:00
index.html Swagger: Add integrity attributes (#48396) 2022-05-02 09:49:49 +02:00
Makefile Alerting: Unify Swagger/OpenAPI generation tooling (#46928) 2022-03-31 09:34:46 +02:00
post.json Alerting: Provisioning GET routes for mute timings (#49044) 2022-05-17 13:42:48 -05:00
README.md Alerting: Unify Swagger/OpenAPI generation tooling (#46928) 2022-03-31 09:34:46 +02:00
spec.json Alerting: Provisioning GET routes for mute timings (#49044) 2022-05-17 13:42:48 -05:00

What

This aims to define the unified alerting API as code. It generates OpenAPI definitions from go structs. It also generates server/route stubs based on our documentation.

Running

make - regenerate everything - documentation and server stubs. make serve - regenerate the Swagger document, and host rendered docs on port 80. view api

Requires

Why

The current state of Swagger extraction from golang is relatively limited. It's easier to generate server stubs from an existing Swagger doc, as there are limitations with producing a Swagger doc from a hand-written API stub. The current extractor instead relies on comments describing the routes, but the comments and actual implementation may drift, which we don't want to allow.

Instead, we use a hybrid approach - we define the types in Golang, with comments describing the routes, in a standalone package with minimal dependencies. From this, we produce a Swagger doc, and then turn the Swagger doc back into a full-blown server stub.