Skip to content

Conversation

@Will-ShaoHua
Copy link
Contributor

@Will-ShaoHua Will-ShaoHua commented Apr 28, 2025

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

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 Profile in the aws.xml schema

Before: 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.

@Will-ShaoHua Will-ShaoHua changed the title Custom feat(amazonq): show all customizations across different profiles May 2, 2025
@Will-ShaoHua Will-ShaoHua marked this pull request as ready for review May 5, 2025 17:26
@Will-ShaoHua Will-ShaoHua requested review from a team as code owners May 5, 2025 17:26
@Will-ShaoHua Will-ShaoHua merged commit e0c91fd into aws:main May 6, 2025
11 of 12 checks passed
@Will-ShaoHua Will-ShaoHua deleted the custom branch May 6, 2025 21:42
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.

4 participants