Mysql has been generating an admin password on default installs for, like,
forever. This workflow should be familiar for many users.
I'd suggest taking the automation tooling into account and how a production
rollout (user-provided password) would fit into the workflow.
Andrew
On Tue, Feb 9, 202
Joe,
In addition to your suggestions, were you thinking of making this processor
disabled by default as well?
Tony
On Tue, Feb 9, 2021, 11:04 PM Joe Witt wrote:
> Team
>
> While secure by default may not be practical perhaps ‘not blatantly wide
> open’ by default should be adopted.
>
> I think
Team
While secure by default may not be practical perhaps ‘not blatantly wide
open’ by default should be adopted.
I think we should consider killing support for http entirely and support
only https. We should consider auto generating a user and password and
possibly server cert if nothing is con
Thanks for clarifying, Matt!
Please ignore everything I said 😶
> On Feb 9, 2021, at 14:41, Matt Burgess wrote:
>
> The PrometheusReportingTask and the NIFi API endpoint for Prometheus
> metrics are different beasts but they use quite a bit of the same code
> [1]. The intent is to report on the
The PrometheusReportingTask and the NIFi API endpoint for Prometheus
metrics are different beasts but they use quite a bit of the same code
[1]. The intent is to report on the same metrics wherever possible,
and I think for the most part we've done that. They don't call each
other, instead they get
Hello and thanks for your interest in contributing to NiFi.
If my understanding is correct, PrometheusReportingTask is an implementation of
the ReportingTask interface that exposes data available in the ReportingContext
and other internal interfaces on the Prometheus Meter Registry and ultimatel
