You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I downloaded my actual VCL file from Fastly and ran the linting, and it didn't find these errors at all. I wonder if the way my backends are being generated from VCL don't include them, and they all get squashed together via Fastly's templating.
Hi @tibbon, thank you for reaching out to our project.
Just to confirm - Is your director will be created via Terraform using this block?
Currently we're fetch Fastly resources only backend, dictionary, acls, snippets, and logging endpoints so director won't be fetched.
I downloaded my actual VCL file from Fastly and ran the linting, and it didn't find these errors at all. I wonder if the way my backends are being generated from VCL don't include them, and they all get squashed together via Fastly's templating.
On the actual generated VCL, Fastly will generate with registered directors so probably the linting will be fine.
If true for my confirmation, we will support director to solve it.
When linting my VCL with falco (via Terraform) I'm getting this error:
Relevant bits of VCL:
In both my custom vcl_recv (and in the snippet Fastly auto-inserts, i should probably de-dupe them) I have:
Expected behavior
Fastly's Director documentation says:
so I'd expect this to be ok.
Desktop
required
The text was updated successfully, but these errors were encountered: