Add support for "bypass_local_route_table" or arbitrary backend flags

[StarpTech]

Hi there,

Due to the limitation of C@E we are forced to add .bypass_local_route_table = true; to all backends that are chained to a C@E service. This is required because Compute @ Edge isn't deployed on all nodes across all POPs globally. Unfortunately, this flag is not available in this module. It would be great to support this flag or to support an untyped dictionary for feature flags in general e.g.

Before you can use bypass_local_route_table the flag must be enabled on your service or account

  dynamic "backend" {
    for_each = var.backends
    content {
      address           = backend.value.origin
      name              = backend.value.origin
      ssl_cert_hostname = backend.value.origin
      override_host     = backend.value.origin
      request_condition = backend.value.origin
      use_ssl           = true
      ssl_check_cert    = true
      port              = 443
      shield = backend.value.shield

      // Solution 1 (preferred)
	  bypass_local_route_table = true
    
	  // Solution 2
	  experimental {
		 .bypass_local_route_table = true
	  }
    }
  }

Desired result per backend.

backend F_YOUR_HOST {
    ......
   .bypass_local_route_table = true
   
}

[Integralist]

Hi @StarpTech thanks for opening this issue.

Supporting .bypass_local_route_table isn't currently possible as it's not supported within the Fastly API.

Even if you were to view the current VCL of your service and copy/paste the backend definition into a VCL Snippet (instead of defining the backend in the Terraform interface using a backend resource) then it still wouldn't work because it would also require a pragma to be applied that can only be done internally by Fastly.

I'll open up a ticket internally to track this as a new feature request, and I'll leave this GitHub issue open until such time we have any feedback I can provide.

Thanks.

[StarpTech]

Hi @Integralist thanks for the fast response. How should I proceed in that case? We need that flag to roll out our services.

[Integralist]

Thanks @StarpTech.

I would say the quickest way forward for right now would be to reach out to your Fastly account manager (either via the Customer Slack or via [email protected]), ping them this GitHub issue if they're not already aware of the issue you're having, and they'll be able to pick this up and get further discussions started.

[StarpTech]

Thanks, I'm already in the process :smile:

[Integralist]

👋🏻 I'm going to close this issue as I've been informed that as of Sept 2022 (approx) this setting is no longer needed.