Hello Dev community, I put together a NIP describing a goal of making data ingress ports created as part of NiFi flow definitions (eg, a ListenHTTP processor) dynamically discoverable [1].
Deploying NiFi in cloud or containerized environments, where network ingress is controlled via an external component such as a gateway, load balancer, or proxy, seems to be the norm for a lot of teams these days. Additionally, through user discussion I see a preference for flow versioning and automated flow deployments to promote new versions from non-prod to prod environments. These factors make it burdensome on operations teams to manage flows that contain Listen processors that require network ingress rules. Dynamic discovery of NiFi flow ingress ports would be a step in the right direction to enable teams to build automated deployment and infrastructure-as-code logic that takes into account flow definitions when creating corresponding, required network rules. The NIP describes how that goal could be achieved, but I'm interested in the community's perspective. Please comment on the Jira with any thoughts or feedback. [1] https://issues.apache.org/jira/browse/NIP-14 Cheers, Kevin
