Skip to content

feat(amazonq): paid tier #7379

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

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

feat(amazonq): paid tier #7379

wants to merge 4 commits into from

Conversation

justinmk3
Copy link
Contributor

Problem

When Builder Id customers hit the "free tier" limit, there is no guidance.

Solution

  • Update to latest Flare release, which:

    • auto-detects when the free-tier limit is reached
    • shows a chat card with an inputbox for aws account id
    • handles when the user clicks "Upgrade"
    • waits for upgrade to complete and updates chat UI
  • Add a Manage Subscriptions menu item, which invokes the Flare aws/chat/manageSubscription command.

  • Handle ShowDocumentParams.external. This is a standard lsp interface, and is required by the new Flare logic.


  • Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
  • Your code changes must meet the guidelines in CONTRIBUTING.md.
  • License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@justinmk3 justinmk3 requested review from a team as code owners May 23, 2025 20:07
Copy link

  • This pull request implements a feat or fix, so it must include a changelog entry (unless the fix is for an unreleased feature). Review the changelog guidelines.
    • Note: beta or "experiment" features that have active users should announce fixes in the changelog.
    • If this is not a feature or fix, use an appropriate type from the title guidelines. For example, telemetry-only changes should use the telemetry type.

@justinmk3 justinmk3 marked this pull request as draft May 23, 2025 20:07
justinmk3 added 4 commits May 27, 2025 20:03
Problem:
LSP server can't open URLs, because the LSP client does not correctly
handle `ShowDocumentParams.external` requests.
LSP spec: https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#showDocumentParams

Solution:
When `ShowDocumentParams.external` is true, open the URL in a web
browser instead of as a editor document.
@justinmk3 justinmk3 marked this pull request as ready for review May 28, 2025 00:05
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.

1 participant