sejal-gupta-ksolves opened a new pull request, #11858:
URL: https://github.com/apache/nifi/pull/11858

   # Summary
   
   [NIFI-16398](https://issues.apache.org/jira/browse/NIFI-16398)
   
   The backend exposes a TROUBLESHOOTING connector state and endpoints to enter 
and end it, but the
   frontend did not recognize the state or offer the actions. This change adds 
both.
   
   Changes:
   - Shared: added `ConnectorState.TROUBLESHOOTING`, the 
`ENTER_TROUBLESHOOTING` and `END_TROUBLESHOOTING`
     action names, `isConnectorInTroubleshooting`, `canEnterTroubleshooting` 
and `canEndTroubleshooting`,
     and mapped TROUBLESHOOTING to the caution status variant.
   - Service: `enterTroubleshooting` (`POST /connectors/{id}/troubleshooting`) 
and `endTroubleshooting`
     (`DELETE /connectors/{id}/troubleshooting`), both sending the current 
revision and
     `disconnectedNodeAcknowledged`.
   - State: listing and canvas-entity actions, effects and reducers. Responses 
replace the stored
     connector entity, failures use the existing error handling, and a 
lifecycle request is ignored while
     another is in flight.
   - UI: "Enter troubleshooting" and "End troubleshooting" in the connector 
listing menu, and buttons in
     the canvas connector info panel. All are shown only when the backend 
`availableActions` allow the
     action and the user has read and operate permission.
   - Tests for the contracts, state detection, status variant, gating, request 
construction, effects,
     reducers, duplicate prevention and UI visibility/events.
   
   Out of scope, as listed in the ticket: advanced-page banners, route guards, 
component run-status
   changes, processor advanced UI, connector-scoped Controller Service editing, 
RPG refresh, alignment
   and provenance replay, and backend changes.
   
   # Verification
   
   Frontend  the same targets CI runs:
   - [x] `npx nx run-many -t lint`
   - [x] `npx nx run-many -t test`
   - [x] `npx nx run-many -t build`
   
   ### Manual testing
   Against a local NiFi with the Kafka-to-S3 connector:
   - Listing: Enter Troubleshooting shows when STOPPED; the state badge turns 
amber TROUBLESHOOTING; End Troubleshooting returns it to STOPPED.
   - Canvas info panel: the same Enter/End buttons appear and work.


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to