(You can automate at least some administrative actions at an "omnipotent" power level with bin/conduit call --method user.edit nowadays, too, although accountadmin operated with interactive prompts so it's unlikely anyone automated on top of it.)

Stuff to fix with subscriptions:

if this is really an issue we could likely throw a rate limit on the action

This is sort-of-quasi-intentional

This is actually slightly tricky.

A related issue is that when object A returns object B as an extended policy check and the user fails the extended policy check, the "PolicyException" dialog is misleading. It reads like this:

Actually, since the modern behavior is reasonable by default (the "Limit" field is not required, and defaults to empty, and the panel works properly if "Limit" is left blank), users have to explicitly set a limit to get any unintuitive behavior here. If they do, they still get a "View All Results" hint.

The bucket limit is currently implemented like this:

It would also be nice to figure out Phortune permissions better here since this is a good opportunity to vet everything.

See PHI1378, which is interested in "at least N", for N = 2.

There was one issue with this: bin/host stop --instance X (which is rarely used, and has no prior automated callers) used --force, which stops all daemons on the host. The recent changes to the --force flag in D20601 also had an indirect impact here. I fixed this and redeployed the repo tier.

See downstream https://phabricator.wikimedia.org/T230001 for a similar issue on project pages.

The repro case is something like:

In D20221#262095, @epriestley wrote:

Oh, good catch. Yeah, that would be an improvement.

use cases seem very weak.