[
https://issues.apache.org/jira/browse/NIFI-16156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18101388#comment-18101388
]
ASF subversion and git services commented on NIFI-16156:
--------------------------------------------------------
Commit b653e0a78f59ccb9c9eecbcd96c2b90e8e423022 in nifi's branch
refs/heads/main from Matt Gilman
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b653e0a78f5 ]
NIFI-16156: Add connector-scoped Controller Service GET so View Canva… (#11487)
* NIFI-16156: Add connector-scoped Controller Service GET so View Canvas Go To
Service works without Troubleshooting.
- Adding response merging for the Controller Service endpoints.
* NIFI-16156: Addressing review feedback.
This closes #11487
> Add connector-scoped Controller Service GET for View Canvas "Go to Service"
> ---------------------------------------------------------------------------
>
> Key: NIFI-16156
> URL: https://issues.apache.org/jira/browse/NIFI-16156
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Reporter: Matt Gilman
> Assignee: Matt Gilman
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In Connector View Canvas mode, clicking "Go to Service" on a property that
> references a Controller Service does not navigate to that service.
> The UI needs the service's parent process group id to route into the
> connector controller-services page. Today that lookup uses `GET
> /controller-services/\{id}`, which returns 409 for connector-managed services
> unless the Connector is in Troubleshooting. View Canvas is read-only and does
> not enter Troubleshooting, so the lookup fails and navigation never happens.
> Connector-scoped APIs already exist for listing controller services in a
> connector process group and for getting/clearing controller service state
> without Troubleshooting. There is no matching single-service GET under the
> Connector API, so the UI has no way to resolve a referenced service by id
> while remaining outside Troubleshooting.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
