Update redteam complexity mapping #40321
Merged
Conversation
This file contains 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
There was a problem hiding this comment.
Pull Request Overview
This PR updates the red team complexity mapping logic by modifying how attack strategies are flattened in the formatting utility.
- Changes the mapping for moderate attack strategies by replacing the composed combination with a single strategy.
- Updates the difficult attack strategies mapping by removing one composed combination in favor of a unified strategy.
Comments suppressed due to low confidence (2)
sdk/evaluation/azure-ai-evaluation/azure/ai/evaluation/_red_team/_utils/formatting_utils.py:67
- The moderate block now only adds AttackStrategy.Tense instead of the previously composed combination. Please verify that this change accurately reflects the intended mapping for moderate attack strategies.
AttackStrategy.Tense],
sdk/evaluation/azure-ai-evaluation/azure/ai/evaluation/_red_team/_utils/formatting_utils.py:73
- In the difficult block, removal of AttackStrategy.Morse and merging the Base64 strategy into a single Compose call changes the behavior. Please confirm that this modification aligns with the intended design for difficult attack strategies.
AttackStrategy.Base64
github-actions
bot
added
the
Evaluation
nagkumar91
approved these changes
Apr 1, 2025
|
API change check APIView has identified API level changes in this PR and created following API reviews. |
nagkumar91
approved these changes
Apr 1, 2025
nagkumar91
approved these changes
Apr 1, 2025
…-sdk-for-python into fix-complexity
nagkumar91
approved these changes
Apr 2, 2025
nik1097
pushed a commit
to nik1097/azure-sdk-for-python
that referenced
this pull request
Apr 5, 2025
* Update complexity mapping * remove unused debug_mode param * update strategy converter mapping * get base64 tense working properly * Add api version if its available in model config * fix printing errors * make red_team separate sub-package and fix unit tests * update sample * Update setup.py to pin pyrit and termcolor * Update setup.py * fix unit tests --------- Co-authored-by: Nagkumar Arkalgud <nagkumar@naarkalg-work-mac.local> Co-authored-by: Nagkumar Arkalgud <nagkumar91@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines