fix(amazonq): Remove setSystemCertificates from proxyUtil #7558
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
We enabled experimental proxy support in FLARE in this PR. The ProxyConfigManager within FLARE gathers and injects OS CAs. See here.
The current
setSystemCertificates()call also extracts system certificates and setsNODE_EXTRA_CA_CERTS/AWS_CA_BUNDLE. This duplicates and can even override our custom logic, leading to unpredictable CA bundles.Solution
setSystemCertificates()method from proxy util.All certificate loading now flows through a single code path (
ProxyConfigManager.getCertificates()), eliminating conflicts and ensuring consistent OS CA handling.Testing
feature/xbranches will not be squash-merged at release time.