feat: add per-provider TLS and proxy configuration#6025
Closed
maxious wants to merge 1 commit intoanomalyco:devfrom
Closed
feat: add per-provider TLS and proxy configuration#6025maxious wants to merge 1 commit intoanomalyco:devfrom
maxious wants to merge 1 commit intoanomalyco:devfrom
Conversation
Add support for configuring TLS options and HTTP proxy per provider, enabling use of corporate proxies, self-signed certificates, and mTLS. New provider options: - tls.rejectUnauthorized: Accept self-signed certificates - tls.cert: Client certificate path for mTLS - tls.key: Client private key path for mTLS - tls.ca: Custom CA certificate path(s) - proxy: HTTP proxy URL (overrides HTTPS_PROXY env var) The TLS config is passed to Bun's native fetch using Bun.file() for cert/key/ca paths. The proxy option uses Bun's built-in proxy support. For system-wide certificate trust, users can set: - NODE_OPTIONS="--use-system-ca" or BUN_OPTIONS="--use-system-ca" - NODE_EXTRA_CA_CERTS=/path/to/ca.pem Fixes anomalyco#1694 - Users with corporate CAs can now either use the system trust store via --use-system-ca flag, or specify their CA cert path in the provider's tls.ca option. Documentation added to packages/web/src/content/docs/network.mdx with examples for proxy configuration, custom CAs, and mTLS setup.
maxious
force-pushed
the
mtls-proxy-support
branch
from
0c8f447 to
14b64d4
Compare
opencode-agent
bot
force-pushed
the
dev
branch
from
00637c0 to
71e0ba2
Compare
thdxr
force-pushed
the
dev
branch
3 times, most recently
from
f1ae801 to
08fa7f7
Compare
Contributor
|
Closing this pull request because it has had no updates for more than 60 days. If you plan to continue working on it, feel free to reopen or open a new PR. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add support for configuring TLS options and HTTP proxy per provider, enabling use of corporate proxies, self-signed certificates, and mTLS.
New provider options:
The TLS config is passed to Bun's native fetch using Bun.file() for cert/key/ca paths. The proxy option uses Bun's built-in proxy support.
For system-wide certificate trust, users can set:
Documenting this resolves #1694 - Users with corporate CAs can now either use the system trust store via --use-system-ca flag, or specify their CA cert path in the provider's tls.ca option.
Documentation added to packages/web/src/content/docs/network.mdx with examples for proxy configuration, custom CAs, and mTLS setup.