fix: use update-backlog-task for mitigation#1
Open
bhavanik03 wants to merge 1 commit into
Open
Conversation
bhavanik03
force-pushed
the
fix/mitigation-workflow
branch
from
c46be7c to
b82ae25
Compare
…-task The correct way to trigger mitigation plan generation is: aws devops-agent update-backlog-task --task-status PENDING_START NOT creating a new investigation. The old approach created a separate task with no context from the original RCA. Mitigation plans are stored as mitigation_summary_md journal records. Retrieve via: list-executions → list-journal-records --record-type mitigation_summary_md
bhavanik03
force-pushed
the
fix/mitigation-workflow
branch
from
b82ae25 to
69f724d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…-task
The correct way to trigger mitigation plan generation is:
aws devops-agent update-backlog-task --task-status PENDING_START
NOT creating a new investigation. The old approach created a separate task with no context from the original RCA.
Mitigation plans are stored as mitigation_summary_md journal records. Retrieve via: 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.