bbende commented on a change in pull request #4420:
URL: https://github.com/apache/nifi/pull/4420#discussion_r481306447
##########
File path:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/api/FlowResource.java
##########
@@ -2691,6 +2691,39 @@ public Response getAction(
return generateOkResponse(entity).build();
}
+ @GET
+ @Consumes(MediaType.WILDCARD)
+ @Produces(MediaType.APPLICATION_JSON)
+ @Path("node/status/history")
+ @ApiOperation(
+ value = "Gets configuration history for the node",
+ notes = NON_GUARANTEED_ENDPOINT,
+ response = ComponentHistoryEntity.class,
+ authorizations = {
+ @Authorization(value = "Read - /flow")
+ }
+ )
+ @ApiResponses(
+ value = {
+ @ApiResponse(code = 400, message = "NiFi was unable to
complete the request because it was invalid. The request should not be retried
without modification."),
+ @ApiResponse(code = 401, message = "Client could not be
authenticated."),
+ @ApiResponse(code = 403, message = "Client is not
authorized to make this request."),
+ @ApiResponse(code = 404, message = "The specified resource
could not be found."),
+ @ApiResponse(code = 409, message = "The request was valid
but NiFi was not in the appropriate state to process it. Retrying the same
request later may be successful.")
+ }
+ )
+ public Response getNodeHistory() {
+ authorizeFlow();
Review comment:
I think we probably want to move this end-point to the`
ControllerResource` and authorize against `Read - /controller`. The reason
being that most of the information in the node status history is really
controller level information and is similar to what is returned from
`ControllerResource` for` /controller/cluster`.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
