prometheus/discovery/kubernetes
beorn7 747c5ee2b1 Apply analyzer "modernize" to the whole codebase
See
https://pkg.go.dev/golang.org/x/tools/gopls/internal/analysis/modernize
for details.

This ran into a few issues (arguably bugs in the modernize tool),
which I will fix in the next commit, so that we have transparency what
was done automatically.

Beyond those hiccups, I believe all the changes applied are
legitimate. Even where there might be no tangible direct gain, I would
argue it's still better to use the "modern" way to avoid micro
discussions in tiny style PRs later.

Signed-off-by: beorn7 <beorn@grafana.com>
2025-08-27 14:48:41 +02:00
..
endpoints.go Apply analyzer "modernize" to the whole codebase 2025-08-27 14:48:41 +02:00
endpoints_test.go feat(discovery/kubernetes): allow attaching namespace metadata 2025-07-03 19:41:08 +02:00
endpointslice.go Apply analyzer "modernize" to the whole codebase 2025-08-27 14:48:41 +02:00
endpointslice_test.go feat(discovery/kubernetes): allow attaching namespace metadata 2025-07-03 19:41:08 +02:00
ingress.go Apply analyzer "modernize" to the whole codebase 2025-08-27 14:48:41 +02:00
ingress_test.go Apply analyzer "modernize" to the whole codebase 2025-08-27 14:48:41 +02:00
kubernetes.go Apply analyzer "modernize" to the whole codebase 2025-08-27 14:48:41 +02:00
kubernetes_test.go Apply analyzer "modernize" to the whole codebase 2025-08-27 14:48:41 +02:00
metrics.go chore: enable unused-parameter from revive 2025-02-19 19:50:28 +01:00
node.go Apply analyzer "modernize" to the whole codebase 2025-08-27 14:48:41 +02:00
node_test.go Parallelize discovery/kubernetes tests using t.Parallel() 2024-11-14 10:44:03 +05:30
pod.go Apply analyzer "modernize" to the whole codebase 2025-08-27 14:48:41 +02:00
pod_test.go Apply analyzer "modernize" to the whole codebase 2025-08-27 14:48:41 +02:00
service.go Apply analyzer "modernize" to the whole codebase 2025-08-27 14:48:41 +02:00
service_test.go feat(discovery/kubernetes): allow attaching namespace metadata 2025-07-17 09:53:16 +02:00