Open Bug 1777554 Opened 3 years ago Updated 3 years ago

Add an option to control whether update is disabled

Categories

(Testing :: mozregression, enhancement, P3)

Firefox 104
enhancement

Tracking

(Not tracked)

People

(Reporter: bytesized, Unassigned)

References

Details

Attachments

(1 file)

Application update is automatically disabled by mozregression. This is done by setting app.update.enabled and setting the DisableAppUpdate enterprise policy.

This makes it very difficult to find a regression range for update bugs. Could a setting be added to control this so that it could be turned off when finding a regression for update bugs?

:bytesized -- for the prefs (e.g. app.update.enabled or app.update.auto) you should be able to pass those via the --pref argument (at least in the CLI). For the policy, it is currently hardcoded and I don't think there's a way to achieve that right now without some code changes.

It looks like for policies, we just overwrite the whole file with {"policies": {"DisableAppUpdate": True}}. So one option is to add an argument that allows overriding policy keys/values, and make that available to the launcher before it starts (which currently does not have access to any of the arguments before it starts).

Severity: -- → N/A
Priority: -- → P3

(In reply to Zeid Zabaneh [:zeid] from comment #1)

So one option is to add an argument that allows overriding policy keys/values, and make that available to the launcher before it starts

That would work just great.

See Also: → 1781111
See Also: → 1781813
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: