1777229 - Enforce mandatory "mozillaAddons" permission for privileged temporarily installed addons

Status: NEW

(WebExtensions :: General, task, P3)

Description

[Luca Greco [:rpl] [:luca] [:lgreco]]

As a followup to Bug 1739114 we want to consider enforcing "mozillaAddons" permissions as an additional mandatory requirement to allow a temporarily installed addon to be considered privileged.

The same kind of requirement is already enforced by the addons-linter and in most cases should be caught early enough by the CI job part of the xpi-template used by the privileged addons repositories, nonetheless we want to make sure the privileged addons developers are going aware of that mandatory requirement even sooner during local development by requiring that for the temporarily installed addons.

Comment 1

[William Durand [:willdurand]]

(In reply to Luca Greco [:rpl] [:luca] [:lgreco] from comment #0)

[...] nonetheless we want to make sure the privileged addons developers are going aware of that mandatory requirement even sooner during local development by requiring that for the temporarily installed addons.

To complement the use case described here: it's entirely possible a developer (e.g. a partner) develops an add-on without our tooling because they don't have access to the mozilla-extensions org on GitHub yet (or to TaskCluster) and they don't use the linter or web-ext during development (because that might be overkill for a simple yet privileged add-on).