mcgilman commented on pull request #5072: URL: https://github.com/apache/nifi/pull/5072#issuecomment-902946492
> Thanks @markap14, great idea with the permissions. I made this adjustment and pushed the changes. Although I agree that generally you should require READ on inherited parameter contexts, I'm wondering more about the case of removing an inherited parameter context. As it is described above (and in the code now), if I suddenly discover I no longer have access to an inherited parameter context (Context B above), I can not remove it from Context A. Perhaps this is okay, in that the solution would be for me to contact the administrator, who could remove it, but I just wanted to point out that users might expect they could at least remove an inherited Context they didn't have access to. This behavior is consistent with permission enforcement around Controller Service references. -- 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]
