9.7 peipkg.repository.reconfigured

  • Event type: peipkg.repository.reconfigured
  • Defined in: peipkg.evman
  • Tier: essential
  • Gating: none — every trust-relevant change is recorded
  • Cardinality: once per changed setting

The record that a repository add changed one of an existing repository's trust-relevant settings. One record for each setting that changed, written after the add's own peipkg.repository.added. The settings are signature_policy, allow_insecure_transport, max_trusted_age_days, min_index_version, max_index_staleness_days and trust_anchors.

Only a change made through the flags of repo add is seen. An operator who edits the repository file directly and re-runs the ceremony leaves nothing to compare.

Replaces peipkg.config-change.

9.7.1 Fields #

FieldTypePresenceMeaning
subject.token.sidbin.sidrequiredThe user SID of the effective token the operation ran under.
object.repository.namestrrequiredThe repository the event is about, by the name it is configured under.
config.namestrrequiredThe setting's name as written in the repository file.
config.textstrwhen config.name == signature_policyA setting's value in force, where the value is not an integer: a string, or the textual rendering of a value of another registry type.
config.text-previousstrwhen config.name == signature_policyThe text value a change replaced, beside config.text.
config.valueuintoptionalThe setting in force, for every setting except signature_policy: a number of days or an index version as written, 0 for a setting left at its default; 1 or 0 for allow_insecure_transport; for trust_anchors, how many anchors are configured, so replacing one anchor with another records equal counts.
config.value-previousuintoptionalThe setting it replaced, in the same form as config.value.

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.

Edit this page