Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/2497
@mosermw @markap14 It's kind of a gray area. I suggested an endpoint like
the /nifi-api/flow/about because that seemed like the best fit currently and
was obviously trying to avoid requiring another request to load the UI. I'm a
little hesitant to go the route of a /nifi-api/flow/properties endpoint because
I'm not sure that's a concept we want to advertise/expose. I don't mind doing
something more generic, but what if the concept was more related to default
values or config. This is something that any client using the API may want to
know ahead of time for this reason exactly. Would adding a DefaultsDTO or
ConfigDTO which is set on the AboutDTO fit a little better?
---
