Today, there are a few limitations with our DNS tooling.
The first is that the name of the DNS name generated is always fixed as {service}.{environment}.{application}.customer-domain. I can imagine that folks will want to have control over how their production URLs are constructed, so we should figure out a way to let folks do that.
The second, and I'm not sure if this is as big of a deal, is that every environment gets a DNS name. It may be that some customers only want to enable DNS for certain environments.
The third is, HTTP should redirect to HTTPS.
The fourth is discoverability. Right now customers probably don't know that they can use DNS with their apps because it's a hidden flag. We should detect if a customer has any hosted zones and perhaps prompt them if they'd like to use one of the DNS names.
Today, there are a few limitations with our DNS tooling.
The first is that the name of the DNS name generated is always fixed as
{service}.{environment}.{application}.customer-domain. I can imagine that folks will want to have control over how their production URLs are constructed, so we should figure out a way to let folks do that.The second, and I'm not sure if this is as big of a deal, is that every environment gets a DNS name. It may be that some customers only want to enable DNS for certain environments.
The third is, HTTP should redirect to HTTPS.
The fourth is discoverability. Right now customers probably don't know that they can use DNS with their apps because it's a hidden flag. We should detect if a customer has any hosted zones and perhaps prompt them if they'd like to use one of the DNS names.