On 27/05/2020 07:50, Brian Brazil wrote:
On Wed, 27 May 2020 at 07:05, Ben Kochie <[email protected]
<mailto:[email protected]>> wrote:
I was thinking about building an "exporter kit" repo that would
include some helpful functions to reduce the amount of boilerplate
needed to write exporters.
I've thought such a thing would be useful for a long time, though my
presumption was always that it would end up in client_golang as it's
not too far from instrumentation.
In general I'm not a big fan of widespread proliferation of repos,
particularly if it's lots of tiny repos. Even in the previous cases
where we managed to get the layering largely right, it still was quite
a pain in terms of overhead and release management if the repos were
being actively developed. A single toolkit-y repo I could live with,
I'd be concerned if we were talking repos beyond that.
How does the release management/overhead differ between several single
purpose repos and a single repo containing independent things in
different directories?
--
Stuart Clark
--
You received this message because you are subscribed to the Google Groups
"Prometheus Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/prometheus-developers/f85f5a2e-fcdf-82e6-bcb7-878f9e90c3b7%40Jahingo.com.
