Add event type information for max_file_size attribute
What does this MR do and why?
This MR resolves the following issues:
- #369345 (closed)
- #369344 (closed)
- #369343 (closed)
- #369342 (closed)
- #369341 (closed)
- #369340 (closed)
... which are described in this epic and it's parent epic
All these issues were included in this MR because all affect the same two files only.
How to set up and validate locally (via UI)
1. (pre-requisite) Add Group audit events Stream
- Go to
Menu -> Groups -> [Select Group] -> Security & Compliance -> Audit Events
- Click on
Streams
tab - Add a Stream URL in Group audit events. Tip: https://webhook.site
2. Change the push rules for the group
- Go to
Menu -> Groups -> [Select Group] -> Settings -> Repository
- Expand
Pre-defined push rules
section - Change
Maximum file size (MB)
field. - Change
Prohibited file names
regex field. - Change
Commit author's email
regex field. - Change
Reject expression in commit messages
regex field. - Change
Require expression in commit messages
regex field. - Change
Branch name
regex field.
- Wait for the response in your stream/webhook (step 1).
It will look like the following:
The same for the rest of the events, looking like this in these jsons:
{
...
"entity_type": "Group",
"target_type": "PushRule",
"event_type": "group_push_rules_max_file_size_updated"
}
{
...
"entity_type": "Group",
"target_type": "PushRule",
"event_type": "group_push_rules_branch_name_regex_updated"
}
{
...
"entity_type": "Group",
"target_type": "PushRule",
"event_type": "group_push_rules_commit_message_regex_updated"
}
{
...
"entity_type": "Group",
"target_type": "PushRule",
"event_type": "group_push_rules_commit_message_negative_regex_updated"
}
{
...
"entity_type": "Group",
"target_type": "PushRule",
"event_type": "group_push_rules_author_email_regex_updated"
}
{
...
"entity_type": "Group",
"target_type": "PushRule",
"event_type": "group_push_rules_file_name_regex_updated"
}
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by David Elizondo