+1 also in favor of eventual support.
The primary case I hope to use wildcard support for can well be solved by individual subdomains. What I would really have loved to do for a long time now is simply…
https://fc353094d1dee.api.client.com
https://dff397b15db53.api.client.com
etc…
The wildcard in this case being a placeholder for an account’s API key. In this situation I’d actually rather manage the individual certificates server-side on the VPN using an internal authority and wildcard on the client-facing side. (i,e. servers reject non-validating subdomains internally but present the wildcard cert to the internet)
I wonder if any of you have any recommendations? An added benefit to using wildcard is a reduction in requests to LetsEncrypt registration servers.