ChenSammi commented on PR #5203: URL: https://github.com/apache/ozone/pull/5203#issuecomment-1697161036
> > As per @ChenSammi suggested to have specified admin user under "ozone.administrators" config based on test case, it can be handled > > Would OM admin be considered an SCM admin by default? I'm not sure we want this, but if we do not do it this way it would be a breaking change because all users would need to update their admin configs. Currently, the "ozone.administrators" applies to both OM and SCM. There is no individual property to control OM or SCM admins. And both OM and SCM will add the user who launches the services as admin. Generally, the user who launches OM, will launches SCM too, so it will not be a general problem. Before this PR, there is already admin check on getContainerWithPipeline. This PR add the check to other APIs, so the behavior is consistent. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
