[jira] [Commented] (NIFI-6043) Indicate deprecated components on canvas

["Pierre Villard (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771057#comment-16771057 ] 

Pierre Villard commented on NIFI-6043:
--------------------------------------

Hey [~alopresto] - I just added a link to NIFI-5555 which is pretty similar. You can close the old one as duplicate (I think yours is more detailed) if that's ok for you.

> Indicate deprecated components on canvas
> ----------------------------------------
>
>                 Key: NIFI-6043
>                 URL: https://issues.apache.org/jira/browse/NIFI-6043
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Core UI
>    Affects Versions: 1.8.0
>            Reporter: Andy LoPresto
>            Priority: Major
>              Labels: deprecated, flow-migration, ui
>
> As some components become deprecated, I feel there can be better indicators of this status for both existing flows and new components during flow development. Some ideas:
> * In the "Add Processor" dialog
>   * Have an icon indicator like "Restricted" which indicates deprecated status and emphasize the deprecation information (shown in component documentation) in the description
>   * Allow users to find deprecated components via a "deprecated" tag in the tag cloud and via text search
> * On the canvas
>   * Have an icon indicator like "Restricted" on the components which indicates deprecated status
>   * Have an easy way to find all instances of deprecated components on the canvas
>   * If possible, have an easy way to migrate all configured instances of deprecated component to suggested replacement (i.e. replace {{GetHTTP}} with {{InvokeHTTP}} configured for {{GET}} method). This may require manual intervention
> Some of these steps may not be easily done through the UI but could be automated/exposed via the NiFi CLI or other API consumers. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)