Skip to content

v0.5.2: incident-context tailoring + display-name vendor resolution

Choose a tag to compare

View all tags
@cyanheads cyanheads released this 11 Jul 02:04
v0.5.2
This tag was signed with the committer’s verified signature.
cyanheads Casey Hand
SSH Key Fingerprint: lkZCAfVCK5qsrcvEYCs0BnVRDCX7pKsdCZkw5yYKMuw
Verified
Learn about vigilant mode.
392e8b8
This commit was signed with the committer’s verified signature.
cyanheads Casey Hand
SSH Key Fingerprint: lkZCAfVCK5qsrcvEYCs0BnVRDCX7pKsdCZkw5yYKMuw
Verified
Learn about vigilant mode.

incident-context tailoring + display-name vendor resolution

devops_suggest_action now tailors its playbook to the incident context and resolves a vendor by display name as well as slug.

Added:

  • Incident-context tailoring — affected_components / incident_summary prepend a targeted subsystem section (CI/CD, DNS, replication/failover, login/sessions) ahead of the generic playbook and add a detailed devops_status_check re-check (#21)

Fixed:

  • Vendor resolution accepts a display name ("Amazon Web Services"), not just a slug, so vendor_category and the pre-filled follow-up args stay valid; an ambiguous bare word stays unresolved (#20)
  • incident_snippet carries the full incident_summary instead of clipping it to 200 characters (#21)

224 tests pass; bun run devcheck clean.

CHANGELOG v0.5.2

Assets 3
Loading