fix(amazonq): fix for honouring the index cache dir path value #1448
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
awschristou
approved these changes
May 28, 2025
This was referenced May 28, 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.
Problem
The Workspace Indexing settings in Amazon Q are not functioning as expected. Specifically, when changing the cache location for indexing, the indexing files are not being stored in the newly specified location.
Solution
This PR has a fix to ensure that Amazon Q honors the index cache directory path value set by the user. This change ensures that indexing files are correctly stored in the newly specified location when the cache location is modified.
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.