Skip to content

fix(amazonq): Invalidate Obsolete Customization on Profile Switch #5575

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 34 commits into from
Apr 15, 2025

Conversation

evanliu048
Copy link
Contributor

@evanliu048 evanliu048 commented Apr 14, 2025

Types of changes

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

Description

When a user switches profiles, the active customization is now verified against the updated list of available customizations.

If the active customization is not present in the newly returned list, it is automatically invalidated.

This change ensures consistency between the user's profile and the customizations applied.

Checklist

  • My code follows the code style of this project
  • I have added tests to cover my changes
  • A short description of the change has been added to the CHANGELOG if the change is customer-facing in the IDE.
  • I have added metrics for my changes (if required)

License

I confirm that my contribution is made under the terms of the Apache 2.0 license.

@evanliu048 evanliu048 requested review from a team as code owners April 14, 2025 23:42
Copy link
Contributor

@manodnyab manodnyab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you please add a changelog?

@evanliu048 evanliu048 merged commit 354dede into aws:main Apr 15, 2025
14 checks passed
rli pushed a commit that referenced this pull request Apr 21, 2025
…f an Idc connection (#5591)

Follow-up to #5575.

As mentioned in that PR:

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.

In other words, each Q profile has access to its own set of customizations.

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

5 participants