You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2020/09/07 07:42:07 UTC

[GitHub] [druid] pjain1 commented on issue #9380: Fine grained config and state resources

pjain1 commented on issue #9380:
URL: https://github.com/apache/druid/issues/9380#issuecomment-688111518


   @jon-wei I think its a good suggestion to namespace new permissions perhaps like prepending `v1` so for example read datasource  will look like - `v1:read:datasource:*`. The new permissions can stay in namespace or other depending on the auth implementation, so the users will define the new permissions in their auth system and assign it to users. Once all the new permissions are defined they can set a flag in properties file which will tell Druid to use new permission model. This will make it seamless for users to upgrade, the only condition would be to flip the switch only after all the nodes in cluster are running the latest code.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org