Open bdelacretaz opened 5 years ago
What's being left over is the backend that has been defined for the proxy strain, so it is specific to proxies. We can (with some accuracy) detect the backends we have generated, so theoretically it is possible to remove them, but either way there are downsides:
I think this relates to the question of ownership of the fastly service. If we can agree, that helix has 100% ownership of the service, then the strain config should be the single source of truth that generates the VCL and configures the service.
as mentioned elsewhere, this could imply that for tricky setups, our service would act as backend of another service. the more I think of it, the more I like it. the only problem will be cache invalidation.
Description The VCL of my "playground" Fastly service contains leftovers from previously defined strains which are not in my Helix config anymore.
To Reproduce
In my case the VCL of my
bdelacre - playground - bertrand.helix-demo.xyz
contains leftovers of aF_Proxyincubatorapacheorg4774
proxy strain, a definition:Which AFAICS is used in a single expression later:
Expected behavior Unused strains should be removed from the VCL. I haven't seen any concrete problems with this so far but such leftovers would at least be confusing when debugging things.
Version:
hlx --version 4.4.1