mirror of
https://github.com/coder/coder.git
synced 2026-09-24 15:04:27 +08:00
refactor: clarify MITM certificate naming in aibridgeproxyd (#22408)
## Description Renames internal fields, variables, and comments related to the proxy's certificate/key configuration to explicitly reference their MITM CA purpose. The AI Bridge Proxy uses a CA certificate to sign dynamically generated leaf certificates during MITM interception of HTTPS traffic from AI clients. With the upcoming introduction of TLS listener certificates (for serving the proxy itself over HTTPS, implemented upstack https://github.com/coder/coder/pull/22411), the previous generic naming would become ambiguous. This refactor makes it clear which certificate is which. No user-facing flags, environment variables, YAML keys, or JSON fields were changed, this is purely an internal rename to avoid confusion going forward. Related to https://github.com/coder/internal/issues/1335
This commit is contained in:
Generated
+2
-2
@@ -1920,7 +1920,7 @@ The address the AI Bridge Proxy will listen on.
|
||||
| Environment | <code>$CODER_AIBRIDGE_PROXY_CERT_FILE</code> |
|
||||
| YAML | <code>aibridgeproxy.cert_file</code> |
|
||||
|
||||
Path to the CA certificate file for AI Bridge Proxy.
|
||||
Path to the CA certificate file used to intercept (MITM) HTTPS traffic from AI clients. This CA must be trusted by AI clients for the proxy to decrypt their requests.
|
||||
|
||||
### --aibridge-proxy-key-file
|
||||
|
||||
@@ -1930,7 +1930,7 @@ Path to the CA certificate file for AI Bridge Proxy.
|
||||
| Environment | <code>$CODER_AIBRIDGE_PROXY_KEY_FILE</code> |
|
||||
| YAML | <code>aibridgeproxy.key_file</code> |
|
||||
|
||||
Path to the CA private key file for AI Bridge Proxy.
|
||||
Path to the CA private key file used to intercept (MITM) HTTPS traffic from AI clients.
|
||||
|
||||
### --aibridge-proxy-upstream
|
||||
|
||||
|
||||
Reference in New Issue
Block a user