[
https://issues.apache.org/jira/browse/NIFIREG-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Bende updated NIFIREG-212:
--------------------------------
Fix Version/s: 0.5.0
> 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
> Fix For: 0.5.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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/%[email protected]%3E
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
