You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Bryan Bende (JIRA)" <ji...@apache.org> on 2019/05/30 15:12:00 UTC

[jira] [Assigned] (NIFIREG-212) Add detailed proxy policy configuration

     [ https://issues.apache.org/jira/browse/NIFIREG-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Bende reassigned NIFIREG-212:
-----------------------------------

    Assignee: Bryan Bende

> Add detailed proxy policy configuration
> ---------------------------------------
>
>                 Key: NIFIREG-212
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-212
>             Project: NiFi Registry
>          Issue Type: Improvement
>            Reporter: Koji Kawamura
>            Assignee: Bryan Bende
>            Priority: Major
>
> NiFi Registry should support more granular 'proxy' policy for different NiFi cluster can share the same NiFi Registry instance, but limiting mutation requests (e.g. committing new flow version ... etc) from certain environment.
> For example, if there are dev and prod NiFi clusters, then only allow dev NiFi cluster to update versioned flows. Prod NiFi can only download.
> A detailed use-case was reported to NiFi user mailing list.
> https://mail-archives.apache.org/mod_mbox/nifi-users/201811.mbox/%3CDFEADA92-56D6-480C-B3F9-B101EDEE474D@ncr.com%3E



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