feat(amazonq): show all customizations across different profiles #5646
Conversation
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
Will-ShaoHua
changed the title
Will-ShaoHua
commented
May 2, 2025
.../toolkits/jetbrains/services/codewhisperer/customization/CodeWhispererCustomizationDialog.kt
Outdated
Show resolved
Hide resolved
Will-ShaoHua
commented
May 2, 2025
.../toolkits/jetbrains/services/codewhisperer/customization/CodeWhispererCustomizationDialog.kt
Outdated
Show resolved
Hide resolved
andrewyuq
approved these changes
May 6, 2025
manodnyab
approved these changes
May 6, 2025
leigaol
approved these changes
May 6, 2025
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.
Types of changes
Description
It effectively brings back #5591 by reverting "revert pr" #5612
Also it includes the patch pr #5611 for backward compatibility since previously the persisted customization doesn't have
Profilein theaws.xmlschemaBefore: Customizations were bound to a specific IDC instance.
After: Customizations are now bound to a specific Q profile. An IDC instance can have multiple Q profiles.
The product team has requested that we show all available customizations across profiles, rather than only those tied to the currently connected profile.
This means that when a user selects a customization that belongs to a different Q profile, the plugin should implicitly switch to that profile. This behavior helps reduce confusion and user churn, since users might not clearly understand which profile grants access to which customizations.
Scenario 1: select customization will change profile if needed (when the new customization is under a different profile)
Screen.Recording.2025-05-05.at.12.45.18.PM.mov
Scenario 2: change profile will switch to foundation model
Screen.Recording.2025-05-05.at.12.47.22.PM.mov
License
I confirm that my contribution is made under the terms of the Apache 2.0 license.