Skip to content

fix(aws-devops-agent): correct mitigation workflow - use update-backlog-task#123

Open
bhavanik03 wants to merge 1 commit into
kirodotdev:mainfrom
bhavanik03:fix/mitigation-workflow
Open

fix(aws-devops-agent): correct mitigation workflow - use update-backlog-task#123
bhavanik03 wants to merge 1 commit into
kirodotdev:mainfrom
bhavanik03:fix/mitigation-workflow

Conversation

@bhavanik03
Copy link
Copy Markdown

…og-task

Mitigation plans are generated via update-backlog-task --task-status PENDING_START (not list-recommendations). Plans are stored as mitigation_summary_md journal records.

Updated POWER.md and steering.md with correct flow:

  1. Investigation COMPLETED
  2. update-backlog-task --task-status PENDING_START
  3. Poll until COMPLETED
  4. list-executions → list-journal-records --record-type mitigation_summary_md

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

…og-task

Mitigation plans are generated via update-backlog-task --task-status PENDING_START
(not list-recommendations). Plans are stored as mitigation_summary_md journal records.

Updated POWER.md and steering.md with correct flow:
1. Investigation COMPLETED
2. update-backlog-task --task-status PENDING_START
3. Poll until COMPLETED
4. list-executions → list-journal-records --record-type mitigation_summary_md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant