Dear developers,
As we will generalize the TLS code in the coming months in the project, I would like to see if there is we can reach consensus in the following topic: - The exporters should not offer a way to visualize the TLS config in the Web UI, as that would expose unneedlessly things like usernames. - The prometheus/AM UI's should not offer a way to visualize the TLS config in the Web UI. - In prometheus, the web tls config should be a second config file, not included in the main file, because it is unmarshalled upon each HTTP request and some config files are pretty huge. - As we plan to make the TLS config reusable, it could somehow be versioned or included "on its own" in the docs, and that could start now already. The exporters and prometheus config would point to that dedicate space in the docs. What do you think? -- Julien Pivotto @roidelapluie -- 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/20200529184904.GA47231%40oxygen.
