agents get a per-agent repo limit in their permissions record, orgs are locked
max_repos (default 0, 0..=100) lives in the agent's agent-permissions record and is edited on its permissions panel. The controller applies each agent's own value as max_repo_creation at CreateForgeUser and to existing accounts on change, restart and every five minutes; agent accounts may not create organizations.
This commit is contained in:
parent
dc0d08b7fb
commit
1edeb5c55d
3 changed files with 763 additions and 58 deletions
|
|
@ -102,7 +102,7 @@ Deadline: hive-forge stops after HIVE_FORGE_DEADLINE seconds (default 900), prin
|
|||
* `comment-show` — Print the body (or full JSON) of a single comment by id
|
||||
* `comment-edit` — Edit an existing comment by id
|
||||
* `clone` — Clone a forge repo (default `-r`/`HIVE_FORGE_REPO`) with credentials autoinjected. Pairs with `pr create --agit`
|
||||
* `repo-create` — Create a forge repo under the current user (or `--org`). Prints the repo URL. Agent accounts can't create repos (limit 0)
|
||||
* `repo-create` — Create a forge repo under the current user (or `--org`). Prints the repo URL. Agent accounts create repos only up to their own limit (0 by default)
|
||||
* `repo-add-collaborator` — Add a collaborator to the active repo (`-r`/`HIVE_FORGE_REPO`) with a permission level. Companion to `repo-create`
|
||||
* `repo-labels` — List every label defined on the repo (name + description), optionally filtered by a name substring
|
||||
* `repo-search` — Search the forge for repositories by keyword, topic, or description
|
||||
|
|
@ -1008,7 +1008,7 @@ Clone a forge repo (default `-r`/`HIVE_FORGE_REPO`) with credentials autoinjecte
|
|||
|
||||
## `hive-forge repo-create`
|
||||
|
||||
Create a forge repo under the current user (or `--org`). Prints the repo URL. Agent accounts can't create repos (limit 0)
|
||||
Create a forge repo under the current user (or `--org`). Prints the repo URL. Agent accounts create repos only up to their own limit (0 by default)
|
||||
|
||||
**Usage:** `hive-forge repo-create [OPTIONS] <NAME>`
|
||||
|
||||
|
|
|
|||
|
|
@ -224,9 +224,11 @@ plain comment show under `last comment`, not `reviews`.
|
|||
|
||||
### Repo management
|
||||
|
||||
Agent accounts can't create repos: swarm-controller sets their
|
||||
repo-creation limit to 0 (see `docs/2-handbook/agents/security.md`), so
|
||||
an operator merge stays the only path to main. Ask the operator to
|
||||
Agent accounts can't create repos unless the operator allows it for that
|
||||
agent: swarm-controller sets the account's repo-creation limit to the
|
||||
agent's own `max_repos`, which is 0 until the operator raises it (see
|
||||
`docs/2-handbook/agents/security.md`), so an operator merge stays the only
|
||||
path to main. Ask the operator to
|
||||
create the repo (for example `agents/<name>`) and add you as a
|
||||
collaborator. Forgejo also disables push-to-create.
|
||||
|
||||
|
|
|
|||
|
|
@ -817,6 +817,21 @@ The agent's **internet** access is its own row beside it: a badge reading
|
|||
restricted, log or unrestricted. Selecting it lists the three modes; picking one does a
|
||||
`PUT` of the mode with the stored permissions beside it.
|
||||
|
||||
The **repositories** row is how many repositories the agent's forge account may
|
||||
create: a badge reading none or `up to N`, in the warning tone above 0. Selecting
|
||||
it opens a number box, 0 to 100, and **save** does a `PUT` of `max_repos` with the
|
||||
stored permissions beside it. A `PUT` that leaves `max_repos` out, and the `DELETE`
|
||||
of **use the default**, keep it. Nothing stored means 0, and the box warns that an
|
||||
agent that may create repositories can add a CI workflow to them, CI workflows run
|
||||
unsandboxed on the CI runner, and that makes it arbitrary code on the runner host.
|
||||
The controller sets the value as Forgejo's `max_repo_creation` on that agent's
|
||||
account: on a new one at creation, and on an existing one within seconds of a save
|
||||
and again after every restart. It also turns off creating organizations on every
|
||||
agent account, whatever the number. Forgejo never reports `max_repo_creation`
|
||||
back, so the controller's log (`agent max repos`) is the record of what it applied
|
||||
to each agent. The controller tries an agent whose account the forge refuses again
|
||||
every five minutes.
|
||||
|
||||
A saved change isn't instant. The hive reads the grant about every 30 seconds
|
||||
and the agent takes it at its next turn. A change to `manage_root_agent`
|
||||
restarts the agent after its current turn. The card reads
|
||||
|
|
|
|||
Loading…
Reference in a new issue