2019-03-05 17:57:07 +00:00
|
|
|
// This file is safe to edit. Once it exists it will not be overwritten
|
|
|
|
|
|
|
|
// Copyright Prometheus Team
|
2019-03-01 15:43:33 +00:00
|
|
|
// Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
// you may not use this file except in compliance with the License.
|
|
|
|
// You may obtain a copy of the License at
|
|
|
|
//
|
|
|
|
// http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
//
|
|
|
|
// Unless required by applicable law or agreed to in writing, software
|
|
|
|
// distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
// See the License for the specific language governing permissions and
|
|
|
|
// limitations under the License.
|
2019-03-05 17:57:07 +00:00
|
|
|
//
|
api: Implement OpenAPI generated Alertmanager API V2
The current Alertmanager API v1 is undocumented and written by hand.
This patch introduces a new Alertmanager API - v2. The API is fully
generated via an OpenAPI 2.0 [1] specification (see
`api/v2/openapi.yaml`) with the exception of the http handlers itself.
Pros:
- Generated server code
- Ability to generate clients in all major languages
(Go, Java, JS, Python, Ruby, Haskell, *elm* [3] ...)
- Strict contract (OpenAPI spec) between server and clients.
- Instant feedback on frontend-breaking changes, due to strictly
typed frontend language elm.
- Generated documentation (See Alertmanager online Swagger UI [4])
Cons:
- Dependency on open api ecosystem including go-swagger [2]
In addition this patch includes the following changes.
- README.md: Add API section
- test: Duplicate acceptance test to API v1 & API v2 version
The Alertmanager acceptance test framework has a decent test coverage
on the Alertmanager API. Introducing the Alertmanager API v2 does not go
hand in hand with deprecating API v1. They should live alongside each
other for a couple of minor Alertmanager versions.
Instead of porting the acceptance test framework to use the new API v2,
this patch duplicates the acceptance tests, one using the API v1, the
other API v2.
Once API v1 is removed we can simply remove `test/with_api_v1` and bring
`test/with_api_v2` to `test/`.
[1]
https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md
[2] https://github.com/go-swagger/go-swagger/
[3] https://github.com/ahultgren/swagger-elm
[4]
http://petstore.swagger.io/?url=https://raw.githubusercontent.com/mxinden/alertmanager/apiv2/api/v2/openapi.yaml
Signed-off-by: Max Leonard Inden <IndenML@gmail.com>
2018-04-26 06:12:49 +00:00
|
|
|
|
|
|
|
package restapi
|
|
|
|
|
|
|
|
import (
|
|
|
|
"crypto/tls"
|
|
|
|
"net/http"
|
|
|
|
|
|
|
|
errors "github.com/go-openapi/errors"
|
|
|
|
runtime "github.com/go-openapi/runtime"
|
|
|
|
middleware "github.com/go-openapi/runtime/middleware"
|
|
|
|
|
|
|
|
"github.com/prometheus/alertmanager/api/v2/restapi/operations"
|
|
|
|
"github.com/prometheus/alertmanager/api/v2/restapi/operations/alert"
|
2019-03-07 16:18:18 +00:00
|
|
|
"github.com/prometheus/alertmanager/api/v2/restapi/operations/alertgroup"
|
api: Implement OpenAPI generated Alertmanager API V2
The current Alertmanager API v1 is undocumented and written by hand.
This patch introduces a new Alertmanager API - v2. The API is fully
generated via an OpenAPI 2.0 [1] specification (see
`api/v2/openapi.yaml`) with the exception of the http handlers itself.
Pros:
- Generated server code
- Ability to generate clients in all major languages
(Go, Java, JS, Python, Ruby, Haskell, *elm* [3] ...)
- Strict contract (OpenAPI spec) between server and clients.
- Instant feedback on frontend-breaking changes, due to strictly
typed frontend language elm.
- Generated documentation (See Alertmanager online Swagger UI [4])
Cons:
- Dependency on open api ecosystem including go-swagger [2]
In addition this patch includes the following changes.
- README.md: Add API section
- test: Duplicate acceptance test to API v1 & API v2 version
The Alertmanager acceptance test framework has a decent test coverage
on the Alertmanager API. Introducing the Alertmanager API v2 does not go
hand in hand with deprecating API v1. They should live alongside each
other for a couple of minor Alertmanager versions.
Instead of porting the acceptance test framework to use the new API v2,
this patch duplicates the acceptance tests, one using the API v1, the
other API v2.
Once API v1 is removed we can simply remove `test/with_api_v1` and bring
`test/with_api_v2` to `test/`.
[1]
https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md
[2] https://github.com/go-swagger/go-swagger/
[3] https://github.com/ahultgren/swagger-elm
[4]
http://petstore.swagger.io/?url=https://raw.githubusercontent.com/mxinden/alertmanager/apiv2/api/v2/openapi.yaml
Signed-off-by: Max Leonard Inden <IndenML@gmail.com>
2018-04-26 06:12:49 +00:00
|
|
|
"github.com/prometheus/alertmanager/api/v2/restapi/operations/general"
|
|
|
|
"github.com/prometheus/alertmanager/api/v2/restapi/operations/receiver"
|
|
|
|
"github.com/prometheus/alertmanager/api/v2/restapi/operations/silence"
|
|
|
|
)
|
|
|
|
|
2019-02-26 11:18:57 +00:00
|
|
|
//go:generate swagger generate server --target ../../v2 --name Alertmanager --spec ../openapi.yaml --exclude-main
|
api: Implement OpenAPI generated Alertmanager API V2
The current Alertmanager API v1 is undocumented and written by hand.
This patch introduces a new Alertmanager API - v2. The API is fully
generated via an OpenAPI 2.0 [1] specification (see
`api/v2/openapi.yaml`) with the exception of the http handlers itself.
Pros:
- Generated server code
- Ability to generate clients in all major languages
(Go, Java, JS, Python, Ruby, Haskell, *elm* [3] ...)
- Strict contract (OpenAPI spec) between server and clients.
- Instant feedback on frontend-breaking changes, due to strictly
typed frontend language elm.
- Generated documentation (See Alertmanager online Swagger UI [4])
Cons:
- Dependency on open api ecosystem including go-swagger [2]
In addition this patch includes the following changes.
- README.md: Add API section
- test: Duplicate acceptance test to API v1 & API v2 version
The Alertmanager acceptance test framework has a decent test coverage
on the Alertmanager API. Introducing the Alertmanager API v2 does not go
hand in hand with deprecating API v1. They should live alongside each
other for a couple of minor Alertmanager versions.
Instead of porting the acceptance test framework to use the new API v2,
this patch duplicates the acceptance tests, one using the API v1, the
other API v2.
Once API v1 is removed we can simply remove `test/with_api_v1` and bring
`test/with_api_v2` to `test/`.
[1]
https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md
[2] https://github.com/go-swagger/go-swagger/
[3] https://github.com/ahultgren/swagger-elm
[4]
http://petstore.swagger.io/?url=https://raw.githubusercontent.com/mxinden/alertmanager/apiv2/api/v2/openapi.yaml
Signed-off-by: Max Leonard Inden <IndenML@gmail.com>
2018-04-26 06:12:49 +00:00
|
|
|
|
|
|
|
func configureFlags(api *operations.AlertmanagerAPI) {
|
|
|
|
// api.CommandLineOptionsGroups = []swag.CommandLineOptionsGroup{ ... }
|
|
|
|
}
|
|
|
|
|
|
|
|
func configureAPI(api *operations.AlertmanagerAPI) http.Handler {
|
|
|
|
// configure the api here
|
|
|
|
api.ServeError = errors.ServeError
|
|
|
|
|
|
|
|
// Set your custom logger if needed. Default one is log.Printf
|
|
|
|
// Expected interface func(string, ...interface{})
|
|
|
|
//
|
|
|
|
// Example:
|
|
|
|
// api.Logger = log.Printf
|
|
|
|
|
|
|
|
api.JSONConsumer = runtime.JSONConsumer()
|
|
|
|
|
|
|
|
api.JSONProducer = runtime.JSONProducer()
|
|
|
|
|
|
|
|
api.SilenceDeleteSilenceHandler = silence.DeleteSilenceHandlerFunc(func(params silence.DeleteSilenceParams) middleware.Responder {
|
|
|
|
return middleware.NotImplemented("operation silence.DeleteSilence has not yet been implemented")
|
|
|
|
})
|
2019-03-07 16:18:18 +00:00
|
|
|
api.AlertgroupGetAlertGroupsHandler = alertgroup.GetAlertGroupsHandlerFunc(func(params alertgroup.GetAlertGroupsParams) middleware.Responder {
|
|
|
|
return middleware.NotImplemented("operation alertgroup.GetAlertGroups has not yet been implemented")
|
|
|
|
})
|
api: Implement OpenAPI generated Alertmanager API V2
The current Alertmanager API v1 is undocumented and written by hand.
This patch introduces a new Alertmanager API - v2. The API is fully
generated via an OpenAPI 2.0 [1] specification (see
`api/v2/openapi.yaml`) with the exception of the http handlers itself.
Pros:
- Generated server code
- Ability to generate clients in all major languages
(Go, Java, JS, Python, Ruby, Haskell, *elm* [3] ...)
- Strict contract (OpenAPI spec) between server and clients.
- Instant feedback on frontend-breaking changes, due to strictly
typed frontend language elm.
- Generated documentation (See Alertmanager online Swagger UI [4])
Cons:
- Dependency on open api ecosystem including go-swagger [2]
In addition this patch includes the following changes.
- README.md: Add API section
- test: Duplicate acceptance test to API v1 & API v2 version
The Alertmanager acceptance test framework has a decent test coverage
on the Alertmanager API. Introducing the Alertmanager API v2 does not go
hand in hand with deprecating API v1. They should live alongside each
other for a couple of minor Alertmanager versions.
Instead of porting the acceptance test framework to use the new API v2,
this patch duplicates the acceptance tests, one using the API v1, the
other API v2.
Once API v1 is removed we can simply remove `test/with_api_v1` and bring
`test/with_api_v2` to `test/`.
[1]
https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md
[2] https://github.com/go-swagger/go-swagger/
[3] https://github.com/ahultgren/swagger-elm
[4]
http://petstore.swagger.io/?url=https://raw.githubusercontent.com/mxinden/alertmanager/apiv2/api/v2/openapi.yaml
Signed-off-by: Max Leonard Inden <IndenML@gmail.com>
2018-04-26 06:12:49 +00:00
|
|
|
api.AlertGetAlertsHandler = alert.GetAlertsHandlerFunc(func(params alert.GetAlertsParams) middleware.Responder {
|
|
|
|
return middleware.NotImplemented("operation alert.GetAlerts has not yet been implemented")
|
|
|
|
})
|
|
|
|
api.ReceiverGetReceiversHandler = receiver.GetReceiversHandlerFunc(func(params receiver.GetReceiversParams) middleware.Responder {
|
|
|
|
return middleware.NotImplemented("operation receiver.GetReceivers has not yet been implemented")
|
|
|
|
})
|
|
|
|
api.SilenceGetSilenceHandler = silence.GetSilenceHandlerFunc(func(params silence.GetSilenceParams) middleware.Responder {
|
|
|
|
return middleware.NotImplemented("operation silence.GetSilence has not yet been implemented")
|
|
|
|
})
|
|
|
|
api.SilenceGetSilencesHandler = silence.GetSilencesHandlerFunc(func(params silence.GetSilencesParams) middleware.Responder {
|
|
|
|
return middleware.NotImplemented("operation silence.GetSilences has not yet been implemented")
|
|
|
|
})
|
|
|
|
api.GeneralGetStatusHandler = general.GetStatusHandlerFunc(func(params general.GetStatusParams) middleware.Responder {
|
|
|
|
return middleware.NotImplemented("operation general.GetStatus has not yet been implemented")
|
|
|
|
})
|
|
|
|
api.AlertPostAlertsHandler = alert.PostAlertsHandlerFunc(func(params alert.PostAlertsParams) middleware.Responder {
|
|
|
|
return middleware.NotImplemented("operation alert.PostAlerts has not yet been implemented")
|
|
|
|
})
|
|
|
|
api.SilencePostSilencesHandler = silence.PostSilencesHandlerFunc(func(params silence.PostSilencesParams) middleware.Responder {
|
|
|
|
return middleware.NotImplemented("operation silence.PostSilences has not yet been implemented")
|
|
|
|
})
|
|
|
|
|
|
|
|
api.ServerShutdown = func() {}
|
|
|
|
|
|
|
|
return setupGlobalMiddleware(api.Serve(setupMiddlewares))
|
|
|
|
}
|
|
|
|
|
|
|
|
// The TLS configuration before HTTPS server starts.
|
|
|
|
func configureTLS(tlsConfig *tls.Config) {
|
|
|
|
// Make all necessary changes to the TLS configuration here.
|
|
|
|
}
|
|
|
|
|
|
|
|
// As soon as server is initialized but not run yet, this function will be called.
|
|
|
|
// If you need to modify a config, store server instance to stop it individually later, this is the place.
|
|
|
|
// This function can be called multiple times, depending on the number of serving schemes.
|
|
|
|
// scheme value will be set accordingly: "http", "https" or "unix"
|
|
|
|
func configureServer(s *http.Server, scheme, addr string) {
|
|
|
|
}
|
|
|
|
|
|
|
|
// The middleware configuration is for the handler executors. These do not apply to the swagger.json document.
|
|
|
|
// The middleware executes after routing but before authentication, binding and validation
|
|
|
|
func setupMiddlewares(handler http.Handler) http.Handler {
|
|
|
|
return handler
|
|
|
|
}
|
|
|
|
|
|
|
|
// The middleware configuration happens before anything, this middleware also applies to serving the swagger.json document.
|
|
|
|
// So this is a good place to plug in a panic handling middleware, logging and metrics
|
|
|
|
func setupGlobalMiddleware(handler http.Handler) http.Handler {
|
|
|
|
return handler
|
|
|
|
}
|