-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FR: Better support for UI toggles #489
Comments
Futhermore, the
…will result in the toggle being "off" in the UI. |
How did you manage to enable the toggle for "Force TLS and enable HSTS"? the example above will add the header, but what about Force TLS? |
@DanOfir sorry, didn't include the full example:
|
Would also like to see this! |
This works for me if I use |
I'd be curious to know if, like gzip and the other settings mentioned so far, the same can be achieved for the apex to www redirect setting? It seems like that creates snippets for recv and error that are hidden in the UI. That might be harder to get the resource naming correct in order for the Terraform configuration to align with the UI settings however! Anyone successfully got that working? |
Hit a small snag on the Force TLS option that I figure is worth documenting, we currently define the following: request_setting {
name = "Generated by force TLS and enable HSTS"
force_ssl = true
xff = ""
} For an existing service with this name with the Likely because a value for terraform-provider-fastly/fastly/block_fastly_service_requestsetting.go Lines 293 to 305 in a22ea5f
It also seems like there's a difference for the value of |
Affected Resource(s)
fastly_service_v1
Currently, there are some settings in the UI that are simply shortcuts to other resources, eg:
Currently, if you want those toggles enabled from Terraform, you have to just match the name exactly, which is kind of clumsy:
It would be nice if either:
It can be alarming looking at the UI, thinking these settings aren't enabled, when in fact they are, but the toggles may not be active.
The text was updated successfully, but these errors were encountered: