expose user notification_level to the api
What does this MR do?
Expose the notification_level attribute for users to allow modification by the rest api.
Are there points in the code the reviewer needs to double check?
Easy change and no further checking should be needed.
Why was this MR needed?
When you provision the users and group memberships of users via rest, you (maybe) don't want to inform the users about every change per default. The user are provisioned with disabled notifications and can be put in many groups without flooding the with emails.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
CHANGELOG entry added -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master(if you do - rebase it please) -
Squashed related commits together