Roman Khavronenko bf5b42c2dc vmalert: do not return nil rules for /api/v1/rules (#4344) ... The fix addresses a case when vmalert is configured with a group which has `name`, but doesn't have `rules` configured. In this case it still returns a `nil` instead of `[]` slice. Fixing this via current commit. See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4221 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 66ed6fe62f)		2023-06-05 11:28:00 +02:00
..
vmagent	lib/flagutil/bytes.go: properly handle values bigger than 2GiB on 32-bit architectures	2023-01-10 19:36:23 -08:00
vmalert	vmalert: do not return nil rules for /api/v1/rules (#4344)	2023-06-05 11:28:00 +02:00
vmauth	all: update Go builder from v1.19.3 to v1.19.4	2022-12-11 00:23:32 -08:00
vmbackup	lib/flagutil/bytes.go: properly handle values bigger than 2GiB on 32-bit architectures	2023-01-10 19:36:23 -08:00
vmbackupmanager	docs: update -help output for vmbackup, vmbackupmanager, vmgateway and vmrestore components	2022-06-21 15:49:26 +03:00
vmctl	all: update Go builder from v1.19.3 to v1.19.4	2022-12-11 00:23:32 -08:00
vmgateway	docs: update -help output for vmbackup, vmbackupmanager, vmgateway and vmrestore components	2022-06-21 15:49:26 +03:00
vminsert	app: fix make publish-* after ed93330e66	2022-07-14 11:01:34 +03:00
vmrestore	lib/flagutil/bytes.go: properly handle values bigger than 2GiB on 32-bit architectures	2023-01-10 19:36:23 -08:00
vmselect	app/vmselect/promql: prevent from cannot unmarshal timeseries from rollupResultCache panic after the upgrade to v1.89.0	2023-03-12 19:11:30 -07:00
vmstorage	lib/flagutil/bytes.go: properly handle values bigger than 2GiB on 32-bit architectures	2023-01-10 19:36:23 -08:00
vmui	deployment/docker: update base docker image from 3.17.3 to 3.18.0	2023-05-12 17:34:27 -07:00