Skip to content

fix(amazonq): Add debug logging to listRegionProfile and increase cache TTL to 60s#8592

Open
chungjac wants to merge 2 commits intoaws:feature/profile-loggingfrom
chungjac:add-listRegionProfile-logging
Open

fix(amazonq): Add debug logging to listRegionProfile and increase cache TTL to 60s#8592
chungjac wants to merge 2 commits intoaws:feature/profile-loggingfrom
chungjac:add-listRegionProfile-logging

Conversation

@chungjac
Copy link
Contributor

@chungjac chungjac commented Feb 21, 2026

Problem

  • need more logging

Solution

  • log requestid for listAvailableProfiles
  • some more logs
  • cache expiration from 60 minutes to 1 minute

Next steps

  • merge and give customer build to use. they will use it and report back the logs

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

Add request ID and profile count logging to each listAvailableProfiles
API call to help diagnose cases where profiles are not loading
(P371865494, V2083780156). Also log early-return conditions and
summary after all regions are queried. Increase cache expiration
from 30s to 60s.
@github-actions
Copy link

  • This pull request modifies code in src/* but no tests were added/updated.
    • Confirm whether tests should be added or ensure the PR description explains why tests are not required.

@chungjac chungjac changed the title Add debug logging to listRegionProfile and increase cache TTL to 60s fix(amazonq): Add debug logging to listRegionProfile and increase cache TTL to 60s Feb 21, 2026
@chungjac chungjac closed this Feb 21, 2026
@chungjac chungjac reopened this Feb 21, 2026
@github-actions
Copy link

  • This pull request modifies code in src/* but no tests were added/updated.
    • Confirm whether tests should be added or ensure the PR description explains why tests are not required.
  • 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.

gniumg-source added a commit to gniumg-source/aws-toolkit-vscode that referenced this pull request Feb 23, 2026
@gniumg-source gniumg-source mentioned this pull request Feb 23, 2026
gniumg-source added a commit to gniumg-source/aws-toolkit-vscode that referenced this pull request Feb 23, 2026
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