9.6 peipkg.repository.added
- Event type:
peipkg.repository.added - Defined in:
peipkg.evman - Tier: essential
- Gating: none — every repository trust ceremony is recorded
- Cardinality: once per repository add
The record that peipkg added a repository and established trust in it, or
tried to and failed. Adding a repository decides whose packages the system
will install, which is why it is essential. A command refused before it
names a base URL, such as repo add <name> for a repository with no
configuration, writes nothing.
Replaces peipkg.repo-add.
9.6.1 Fields #
| Field | Type | Presence | Meaning |
|---|---|---|---|
subject.token.sid | bin.sid | required | The user SID of the effective token the operation ran under. |
object.repository.name | str | required | The repository the event is about, by the name it is configured under. |
object.repository.url | str | required | The base URL of the repository the event is about, which is what identifies it (PSPU §5.36). |
outcome.success | bool | required | Whether the operation succeeded. |
outcome.reason | str.enum | when outcome.success == false | Why the operation resolved the way it did. Values here (open set): stale · busy · denied · unowned · alternate-upgrade · unresolvable · untrusted · failed. |
outcome.detail | str | optional | The error as peipkg reported it to the operator. Absent on success. |
Every record also carries the header fields of the envelope, which no payload repeats.
Generated from peipkg.evman by pkm/tools/gen-events-book.py. Edit the fragment, not this page.