Fluxion::Config::StepParser
Entry points the manifest mapper uses.
Most plan kinds have the same spec fields as their stable-schema
counterpart, so they go through build_kind and reuse one parser. Only the
kinds whose shape genuinely differs — the package family, where the manager
comes from the kind id rather than a field — get their own function here.
Constants
Options an APT source line may carry. Anything else — notably trusted
and allow-insecure — is a trust bypass and is rejected rather than
passed through.
Every type the stable jobs/steps schema accepts, in the order the
documentation lists them. kinds and the did-you-mean suggester both
read this, so adding a kind here is the only edit needed.
Names that almost always carry a secret. Getting this wrong in the safe
direction only costs a <redacted> in the output; getting it wrong the
other way leaks a token into logs and state.
Instance methods
Builds a step from a plan entry's spec node using the stable schema's
parser for that type.