alertmanager/.gitignore

/data/
/alertmanager
/amtool
*.yml
*.yaml
/.build
/.release
/.tarballs

!.golangci.yml
!/cli/testdata/*.yml
!/cli/config/testdata/*.yml
!/doc/examples/simple.yml
!/circle.yml
!/.travis.yml
!/.promu.yml
!/api/v2/openapi.yaml
New release process using docker, circleci and a centralized building tool 2015-12-19 23:45:57 +00:00			`/data/`
			`/alertmanager`
Amtool implementation (#636) * Implement alertmanager cli tool 'amtool' The primary goal of an alertmanager tool is to provide a cli interface for the prometheus alertmanager. My vision for this tool has two parts: - Silence management (query, add, delete) - Alert management (query, maybe more in future?) Resolves: #567 2017-04-20 09:04:17 +00:00			`/amtool`
ignore YAML files 2015-07-01 15:56:38 +00:00			`*.yml`
Fix .gitignore and include alertmanager API package 2015-10-02 10:41:41 +00:00			`*.yaml`
New release process using docker, circleci and a centralized building tool 2015-12-19 23:45:57 +00:00			`/.build`
			`/.release`
			`/.tarballs`

Add .golangci.yml Signed-off-by: Simon Pasquier <spasquie@redhat.com> 2019-04-25 08:44:57 +00:00			`!.golangci.yml`
[amtool] use kingpin.v2 (#1330) * Use default values to store values from config * fix typo and reserved keywork * move to long help texts * add one more unit test for resolver * update comments Signed-off-by: Simon Pasquier <spasquie@redhat.com> 2018-04-24 07:35:15 +00:00			`!/cli/testdata/*.yml`
			`!/cli/config/testdata/*.yml`
New release process using docker, circleci and a centralized building tool 2015-12-19 23:45:57 +00:00			`!/doc/examples/simple.yml`
			`!/circle.yml`
			`!/.travis.yml`
			`!/.promu.yml`
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/v2/openapi.yaml`