Aditya Charan created NIFI-16076:
------------------------------------
Summary: Context Path support for NiFi Registry Client
Key: NIFI-16076
URL: https://issues.apache.org/jira/browse/NIFI-16076
Project: Apache NiFi
Issue Type: New Feature
Components: Extensions
Affects Versions: 2.10.0
Environment: All
Reporter: Aditya Charan
Fix For: 2.10.0
In connection to NIFI-16075,
NiFi Registry Flow Registry Client needs to as well support Context Path.
Currently, the behaviour is such that if I specify the Registry URL as
[http://hostname:port/path/nifi-registry|http://hostname:port/path/] the
backend searches for /nifi-registry (which is BASE_APPLICATION_PATH for
nifi-registry) at root and only considers the hostname from the URL specified.
It must also consider the context paths being specified so that Registry
deployments made behind a context path can be made accessible via NiFi UI for
Versioning. Currently Registry doesn't support deployments behind context paths
and is forced to serve at Root. This feature is crucial for NiFi and Registry
deployments behind Cloud DNS and critically saves costs and allows for flexible
architectures for Users
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
