mirror of
https://github.com/odoo/runbot.git
synced 2025-03-27 13:25:47 +07:00
742e3219a6
As the odds of having more projects or more repos with different requirements in the same project, the need to have different sets of reviewers for different repositories increases. As a result, rather than be trivial boolean flags the review info should probably depend on the user / partner and the repo. Turns out the permission checks had already been extracted into their own function so most of the mess comes from testing utilities which went and configured their review rights as needed. Incidentally it might be that the test suite could just use something like a sequence of commoditized accounts which get configured as needed and not even looked at unless they're used.
35 lines
1.2 KiB
Python
35 lines
1.2 KiB
Python
# -*- coding: utf-8 -*-
|
|
|
|
from odoo import http
|
|
from odoo.http import request
|
|
try:
|
|
from odoo.addons.saas_worker.util import from_role
|
|
except ImportError:
|
|
def from_role(_):
|
|
return lambda _: None
|
|
|
|
|
|
class MergebotReviewerProvisioning(http.Controller):
|
|
|
|
@from_role('accounts')
|
|
@http.route(['/runbot_merge/get_reviewers'], type='json', auth='public')
|
|
def fetch_reviewers(self, **kwargs):
|
|
reviewers = request.env['res.partner.review'].sudo().search([
|
|
'|', ('review', '=', True), ('self_review', '=', True)
|
|
]).mapped('partner_id.github_login')
|
|
return reviewers
|
|
|
|
@from_role('accounts')
|
|
@http.route(['/runbot_merge/remove_reviewers'], type='json', auth='public', methods=['POST'])
|
|
def update_reviewers(self, github_logins, **kwargs):
|
|
partners = request.env['res.partner'].sudo().search([('github_login', 'in', github_logins)])
|
|
partners.write({
|
|
'review_rights': [(5, 0, 0)],
|
|
'delegate_reviewer': [(5, 0, 0)],
|
|
})
|
|
|
|
# Assign the linked users as portal users
|
|
partners.mapped('user_ids').write({
|
|
'groups_id': [(6, 0, [request.env.ref('base.group_portal').id])]
|
|
})
|