It is possible to enable Deno unstable flag on Edge Functions?

[thawankeane]

I need to make authenticated fetch API calls through TLS using certificates, the only way that I found to make it is to use the unstable Deno.createHttpClient function. It works locally, but when I deployed to supabase at runtimes it throws an error Deno.createHttpClient is not a function .

My guess is that it may be that supabase edge functions by default do not come with the unstable flag as true. Is there a way to make this work?

[mertyildiran]

@thawankeane Supabase uses Deno Deploy according to this blog post.

By following these discussions and issues:

• How to run a script on deno deploy with --unstable and --no-check flags? denoland/deno#13607
• How to run a script on deno deploy with --unstable and --no-check flags? denoland/deploy_feedback#168
• --unstable on deno deploy denoland/deploy_feedback#22

I found out Deno Deploy is a different runtime than Deno and things like Deno.createHttpClient from the unstable API, are not supported in Deno Deploy. I wish that was not the case, because I really need Deno.createHttpClient in my Edge Functions.

[ardabeyazoglu]

Self-hosted services usually use self-signed certificates with self-signed root certificates. Deno connectTls does not give the option to trust them, which makes us receive the following error in this case. There should be a way of connecting to servers with self-signed certificates i think.

error: Uncaught (in promise) InvalidData: invalid peer certificate: Other(OtherError(UnsupportedCertVersion))

"--unsafely-ignore-certificate-errors" would solve it, but they wouldn't enable this for security. I think there needs to be a way to trust based on specific connection.