Skip to content

Outpost scorers accept a wildcard topic where a specific topic is the point #48

Description

@leggetter

What

topics.includes('*') is accepted in outpost-003, outpost-004 and outpost-005, so a destination subscribed to everything satisfies a check about one topic.

It matters most in outpost-004. The workspace note says "They only want orders on the queue." An agent that creates the SQS destination with topics: "*" passes every check while duplicating the customer's retry traffic onto their queue — which is the "acted more broadly than asked" failure the scenario claims to be about. applyOutpostSeed itself defaults to * when topics are absent, so it is the natural thing to reach for.

In 003 it is arguably right for the primary alert check and wrong for the secondary: accepting * there means an agent can pass without ever learning either topic name, which is most of what that scenario asks.

Done when

Each site decides deliberately whether * counts, and records why. Not a blanket change — for a check that means "would this alert reach them", * genuinely qualifies; for one that means "only these topics", it does not.

Found by an audit of all five Outpost scorers. The other faults it found — a leftover tenant passing 001, attempts counted as deliveries, collateral checks satisfied by the untouched seed — are fixed in #44; this one is not.

Metadata

Metadata

Assignees

No one assigned

    Labels

    harnessRunner, scorers, provisioner and CI

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions