-
Notifications
You must be signed in to change notification settings - Fork 345
Add Policy audit events, and missing Plugin events and fields
#3737
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
Conversation
|
The latest Buf updates on your PR. Results from workflow Buf CI / buf (pull_request).
|
| // visibility is the visibility of the policy. | ||
| buf.alpha.registry.v1alpha1.Visibility visibility = 3; | ||
| // description of the policy. | ||
| string description = 4; |
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.
Why are visibility and description set?
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.
It's additional useful fields in the payload. We already track visibility in other events like the CreateRepository payload, and I'd be inclined to add it to the CreatePlugin event too.
Probably description is not necessary, but I think we need to chat about which fields we want to audit for all of the upcoming policy events, and if we need to add/remove fields in some of the payloads we already have for plugins.
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.
These shared fields should be the same between these entities.
bufdev
left a comment
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 defer to @emcfarlane
CreatePolicy audit eventPolicy audit events, and missing Plugin events and fields
Add some events that the
pluginsdon’t have butrepositoriesdo, for consistency:Add missing field
visibilityforpluginsevents to match the ones we’re already logging forrepositoriesevents.Add the same events, with the same fields, for
policies.