2015-09-25 12:42:14 +00:00
|
|
|
# Copyright 2015 The Prometheus Authors
|
|
|
|
|
# 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-04-16 12:41:18 +00:00
|
|
|
# Needs to be defined before including Makefile.common to auto-generate targets
|
2020-06-09 14:30:55 +00:00
|
|
|
DOCKER_ARCHS ?= amd64 armv7 arm64 ppc64le s390x
|
2019-04-16 12:41:18 +00:00
|
|
|
|
2018-06-13 12:41:52 +00:00
|
|
|
include Makefile.common
|
2015-12-19 23:45:57 +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
|
|
|
FRONTEND_DIR = $(BIN_DIR)/ui/app
|
2015-12-19 23:45:57 +00:00
|
|
|
DOCKER_IMAGE_NAME ?= alertmanager
|
2015-09-25 12:42:14 +00:00
|
|
|
|
2019-01-04 14:37:33 +00:00
|
|
|
STATICCHECK_IGNORE =
|
2015-12-19 23:45:57 +00:00
|
|
|
|
2018-06-13 12:41:52 +00:00
|
|
|
.PHONY: build-all
|
2017-05-12 14:49:32 +00:00
|
|
|
# Will build both the front-end as well as the back-end
|
2018-09-24 13:12:40 +00:00
|
|
|
build-all: assets apiv2 build
|
2017-05-12 14:49:32 +00:00
|
|
|
|
2019-08-26 09:15:28 +00:00
|
|
|
.PHONY: assets
|
|
|
|
|
assets: asset/assets_vfsdata.go
|
|
|
|
|
|
|
|
|
|
asset/assets_vfsdata.go: ui/app/script.js ui/app/index.html ui/app/lib template/default.tmpl
|
|
|
|
|
GO111MODULE=$(GO111MODULE) $(GO) generate $(GOOPTS) ./asset
|
2018-09-24 13:12:40 +00:00
|
|
|
@$(GOFMT) -w ./asset
|
2017-06-07 13:50:44 +00:00
|
|
|
|
2018-11-08 17:46:04 +00:00
|
|
|
ui/app/script.js: $(shell find ui/app/src -iname *.elm) api/v2/openapi.yaml
|
2017-05-12 14:49:32 +00:00
|
|
|
cd $(FRONTEND_DIR) && $(MAKE) script.js
|
2015-09-25 12:42:14 +00:00
|
|
|
|
2018-09-24 13:12:40 +00:00
|
|
|
.PHONY: apiv2
|
2019-03-12 16:11:23 +00:00
|
|
|
apiv2: api/v2/models api/v2/restapi api/v2/client
|
2018-09-24 13:12:40 +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
|
|
|
SWAGGER = docker run \
|
|
|
|
|
--user=$(shell id -u $(USER)):$(shell id -g $(USER)) \
|
|
|
|
|
--rm \
|
|
|
|
|
-v $(shell pwd):/go/src/github.com/prometheus/alertmanager \
|
2021-03-10 18:00:22 +00:00
|
|
|
-w /go/src/github.com/prometheus/alertmanager quay.io/goswagger/swagger:v0.24.0
|
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
|
|
|
|
2019-03-12 16:11:23 +00:00
|
|
|
api/v2/models api/v2/restapi api/v2/client: api/v2/openapi.yaml
|
|
|
|
|
-rm -r api/v2/{client,models,restapi}
|
2019-03-05 17:57:07 +00:00
|
|
|
$(SWAGGER) generate server -f api/v2/openapi.yaml --copyright-file=COPYRIGHT.txt --exclude-main -A alertmanager --target api/v2/
|
2019-03-12 16:11:23 +00:00
|
|
|
$(SWAGGER) generate client -f api/v2/openapi.yaml --copyright-file=COPYRIGHT.txt --skip-models --target api/v2
|
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
|
|
|
|
2018-06-13 12:41:52 +00:00
|
|
|
.PHONY: clean
|
2017-05-12 14:49:32 +00:00
|
|
|
clean:
|
2019-03-05 17:57:07 +00:00
|
|
|
- @rm -rf asset/assets_vfsdata.go \
|
2019-03-12 16:11:23 +00:00
|
|
|
api/v2/models api/v2/restapi api/v2/client
|
2019-03-05 17:57:07 +00:00
|
|
|
- @cd $(FRONTEND_DIR) && $(MAKE) clean
|
