Krikri::Lint::KeyOrderRule
Inherits Krikri::Lint::Rule < Reference < Object
Upstream parity: ansible-lint's key-order (severity LOW, tags formatting). name goes first, block/rescue/always go last; all other keys (including the module) share the middle rank.
Constants
SORTER = ["name", "block", "rescue", "always"] of ::String
Instance methods
applies_to
Sourceid
SourceWhether upstream's transform marks the given violation fixed. Transformable rules that do not mark it fixed get an "Rule specific fix not applied for" ERROR logged for the match.
severity
Sourcetags
Sourcetask_scoped?
Task-oriented: violations belong to an enclosing task, so a
# noqa: anywhere in that task's body suppresses them.
transformable?
Upstream's key-order transform reorders the keys and marks the match fixed for the play and task sub-tags, so no "not applied" is logged.