-
Notifications
You must be signed in to change notification settings - Fork 887
feat: allow auditors to read template insights #10860
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some of these methods are used only by metrics collector, so in theory you don't need to assign auditor permissions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll take another pass and remove the unnecessary perms.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I ended up switching
GetTemplateAppInsightsByTemplate
andGetTemplateInsightsByTemplate
to only checkrbac.ResourceTemplateInsights
as they're only used by metrics collector and it's likely to be lower overhead thanrbac.ResourceTemplate.All()
. Could also have made checkrbac.ResourceSystem
, but I think this is more correct.