Closed grant closed 3 years ago
Provide an option for a developer to bring your own SSL key/cert:
FUNCTION_SSL_KEY
string
key.pem
keys/agent2-key.pem
FUNCTION_SSL_CERT
cert.pem
keys/agent2-cert.pem
What we'd do in the Function Frameworks (very roughly):
Go:
srv := &http.Server{ Addr: ":443", Handler: mux, TLSConfig: cfg, TLSNextProto: make(map[string]func(*http.Server, *tls.Conn, http.Handler), 0), } log.Fatal(srv.ListenAndServeTLS(os.Getenv("FUNCTION_SSL_KEY"), os.Getenv("FUNCTION_SSL_CERT")))
Node:
const options = { key: fs.readFileSync(process.env.FUNCTION_SSL_KEY), cert: fs.readFileSync(process.env.FUNCTION_SSL_CERT) }; https.createServer(options, (req, res) => { res.writeHead(200); res.end('hello world\n'); }).listen(8000);
WDYT @juliehockett?
There are workarounds, like proxying your container with a SSL cert handler. Given that and the number of requests for this feature, closing.
Summary
Provide an option for a developer to bring your own SSL key/cert:
FUNCTION_SSL_KEY
:string
– Path to yourkey.pem
file. i.e.keys/agent2-key.pem
FUNCTION_SSL_CERT
:string
– Path to yourcert.pem
file. i.e.keys/agent2-cert.pem
Examples
What we'd do in the Function Frameworks (very roughly):
Go:
Node:
Reported issues