beorn7 8fdfa52976 API: Promote remote-write-receiver to stable ... Since `/api/v1/write` is a mutating endpoint, we should still activate the remote-write-receiver explicitly. But we should do it in the same way as the other mutating endpoints, i.e. via a flag `--web.enable-remote-write-receiver`. This commit marks the feature flag as deprecated, i.e. it still works but logs a warning on startup. This enables users to seamlessly migrate. With the next minor release, we can start ignoring the feature flag (but still warn a user that is trying to use it). Signed-off-by: beorn7 <beorn@grafana.com>		2022-01-05 15:36:07 +01:00
..
api/v1	Accept promql.Engine interface in v1.NewAPI() (#10050)	2021-12-21 11:22:40 +01:00
ui	Merge pull request #10100 from ddevault/main	2022-01-02 11:41:47 +01:00
federate.go	storage: Consolidate iterator method names (Values -> At) (#9888)	2021-11-29 11:16:40 +01:00
federate_test.go	web: prepare TestFederation_NotReady test for parallel execution	2021-11-10 09:40:43 +01:00
web.go	API: Promote remote-write-receiver to stable	2022-01-05 15:36:07 +01:00
web_test.go	fix missing db.Close() in web_test.go in order to avoid goroutine leak (#10035)	2021-12-20 17:37:53 +05:30