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
The docs about the Terraform Cloud agent currently mention under [Networking Requirements(https://developer.hashicorp.com/terraform/cloud-docs/agents/requirements#networking-requirements) the implementation detail that releases.hashicorp.com is served through Fastly's CDN:
Additionally, the agent must also be able to communicate with any services required by the Terraform code it is executing. This includes the Terraform releases distribution service, releases.hashicorp.com (supported by Fastly), as well as any provider APIs. [...]
At the time of writing, releases.hashicorp.com is no longer served through Fastly's CDN, so this statement is inaccurate and linking to Fastly's IP ranges documentation is misleading.
We'll need to decide here whether to change this documentation to describe the new implementation detail of which CDN this uses, or alternatively to remove the mention of this implementation detail altogether if we don't wish to promise we'll be using our current CDN provider forever.
The text was updated successfully, but these errors were encountered:
dstaley
transferred this issue from hashicorp/terraform-website
Jul 5, 2023
The docs about the Terraform Cloud agent currently mention under [Networking Requirements(https://developer.hashicorp.com/terraform/cloud-docs/agents/requirements#networking-requirements) the implementation detail that
releases.hashicorp.com
is served through Fastly's CDN:At the time of writing,
releases.hashicorp.com
is no longer served through Fastly's CDN, so this statement is inaccurate and linking to Fastly's IP ranges documentation is misleading.We'll need to decide here whether to change this documentation to describe the new implementation detail of which CDN this uses, or alternatively to remove the mention of this implementation detail altogether if we don't wish to promise we'll be using our current CDN provider forever.
The text was updated successfully, but these errors were encountered: