Deploy alias addresses now serve the deploy they name

Every deploy gets an alias address of the form ee-<project>-<target>.cdn.3dge.app, which follows that deployment target to its latest deploy. None of them had ever worked: the edge asked the control plane about the alias, and the control plane only looked for custom domains, so every alias answered “domain not configured”.

Alias addresses now resolve to the deploy they point to. The lookup runs only after both custom-domain lookups miss, so a custom domain always wins, and nothing changes for sites served on their own domain.

The same day, a review of this change found that one account’s deploy could overwrite another account’s alias by choosing the same project and target names, which would have pointed that alias at the wrong site. It was closed about 15 minutes after aliases started resolving: an alias belonging to a different account or project is now refused. The alias lookup also now runs only when a domain is definitely not configured, so a temporary storage error on a customer’s own domain returns an error rather than someone else’s site.

The portal doesn’t currently show a working alias link in production (more on that). The address follows the pattern above: ee-, then your project’s slug and the deployment target’s name, joined with a hyphen.