Comments

Another option would be to write the setup using custom VCL. We do something where we essentially have a base VCL file that calls functions imported from another deploy-specific VCL file. Each Fastly setup that needs customized values just includes its own specific VCL with deployment-specific values in the functions.

It involved 3 haproxy rules per site on the frontend on our side, but we have that all scripted so its a better fit. Also longer term it means we can have our own SSL domain for all things CDN which fits better.