[
https://issues.apache.org/jira/browse/NIFI-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985299#comment-15985299
]
ASF GitHub Bot commented on NIFI-3695:
--------------------------------------
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/1697
@YolandaMDavis Code changes look good. However, one thing I noticed is that
the error provided when the specified proxied user lacks sufficient permissions
could be made a little more user-friendly. Currently, a stack trace reports a
403 response code. It might make sense to consume the response body when the
response code is 4xx or 5xx as it should contain the reason for the failure.
This may provide more details for correcting the issue.
> Create Node Manager & Notification Utilities
> --------------------------------------------
>
> Key: NIFI-3695
> URL: https://issues.apache.org/jira/browse/NIFI-3695
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Tools and Build
> Reporter: Yolanda M. Davis
> Assignee: Yolanda M. Davis
> Fix For: 1.2.0
>
>
> The node manager utility should allow system administrators to connect,
> disconnect or remove a node from a cluster on the command line. If a node is
> not part of a cluster an error message should display if node is not part of
> a cluster. If a node is disconnected from a cluster and needs to be
> connected or removed from that cluster the tool should support receiving a
> list of urls to connected nodes which can be used to send the required
> command to the active cluster.
> The notification utility should allow administrators to send messages as
> bulletins to the NiFi with levels of INFO, WARN or ERROR.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
