Add options for custom https cert and key to config file.

[jamestalmage]

Describe the solution

Currently, the only way to specify custom https certificates is via the command line with --https-key-path and --https-key-path options. I propose those options also be configurable via file under the [dev] section.

[petebacondarwin]

We don't plan to implement this feature but you can achieve the same using .env files and the environment variables that we support: WRANGLER_HTTPS_KEY_PATH and WRANGLER_HTTPS_CERT_PATH.

[jamestalmage]

What rational is used to decide what's command line only and what is config file?

[petebacondarwin]

What rational is used to decide what's command line only and what is config file?

Yeah good question. Basically it is driven by requirements. The original requests were for command line and env var.
We try not to over-implement features since it just adds maintenance burden and increases the surface area for bugs.

Is the workaround above good enough for you, or do you really need it to be configurable in Wrangler confing?

[jamestalmage]

It works fine, I just think it's confusing to add another config file in the mix. My personal preference would be feature-parity between config.toml and the command line, but this will work. The .env option probably should be documented (as I look at what other types of config is done there, I think I understand the rationale better)