[fastly][fastly_service_v1] support vcl snippets

[hashibot]

This issue was originally opened by @mtougeron as hashicorp/terraform#14600. It was migrated here as part of the provider split. The original body of the issue is below.

---

It would be great if the fastly_service_v1 resource supported the VCL Snippets. The way the fastly_service_v1 resource works now we have to update the entire VCL, including the boilerplate, in order to modify just part of the logic (e.g., a Header). This prevents us from being able to use the VCL Snippets and simplifying our code-base & workflow.

[lnrdll]

Any updates on this feature?

[thommahoney]

@rlunardelli I can prioritize this work next.

[rtlechow]

Is this close? Just wondering if I should bother rewriting snippets into custom VCL. Thanks!

[jasonkuhrt]

We need snippets because there is a hard-limit of 3mb on custom vcl but snippets have a soft limit of 1mb. The website says to contact support to get it increased and from my conversation with support they will increase it for everyone sooner or later while the custom vcl limit is firm.

[thommahoney]

@jasonkuhrt Do you use Dynamic Snippets at all or would support for regular (ie. versioned) Snippets suit for your workflow?

[jasonkuhrt]

@thommahoney I think my current use-case will be served by regular snippets just fine as I would put them in custom vcl if I could except there is a 3mb limit. I'm working with Fastly support right now to increase the snippet limit for my fastly services.

[siwyd]

Definitely a big fan of getting this implemented in the provider. It will make our Terraform configs for a lot of services a lot easier to read when we can use snippets instead of having to define custom VCL.

[javapapo]

+1 yes..it would be really nice to have!

[Nightghos]

+1 pleasssee!

[cruzanmo]

+1

[drpebcak]

Is there something blocking #93 from being merged?