v1.1.1

1.1.1 (March 3, 2022)

DOCUMENTATION:

• Add 1.0.0 Migration Guide to Documentation #551

v1.1.0

1.1.0 (February 23, 2022)

ENHANCEMENTS:

• Add fastly_datacenters data resource #540

BUG FIXES:

• Support removing backends from a director #547

DOCUMENTATION:

• Fix fastly-s3 hyperlinks #542

v1.0.0

1.0.0 (February 8, 2022)

ENHANCEMENTS:

• Changes for v1.0.0 #534

BUG FIXES:

• Fix the example usage in docs/index.md #533
• Support Terraform CLI 1.1.4 #536

Migration Guide

Resources omit _v1 suffix:

All resources now have a consistent naming convention which omit the previous v1 suffix.

• fastly_service_v1 -> fastly_service_vcl (renamed with _vcl suffix)
• fastly_service_acl_entries_v1 -> fastly_service_acl_entries
• fastly_service_dictionary_items_v1 -> fastly_service_dictionary_items
• fastly_service_dynamic_snippet_content_v1 -> fastly_service_dynamic_snippet_content
• fastly_user_v1 -> fastly_user

When switching to the new 1.0.0 release, some existing projects might see an error such as:

Error: no schema available for module.fastly.<...> while reading state; this is a bug in Terraform and should be reported

This error is because the Terraform state file will have a different resource name to what's now exposed via the 1.0.0 release. To resolve this issue you'll need to first remove the old resource from the state file and then reimport the data using the new resource name.

As an example, if you had defined an fastly_service_acl_entries_v1 resource, then you could remove and reimport using the following commands (any brackets <...> should be replaced with actual values):

terraform state rm 'fastly_service_acl_entries_v1.<your_resource_name>["<your_acl_name>"]'
terraform import 'fastly_service_acl_entries.<your_resource_name>["<your_acl_name>"]' <service_id>/<acl_id>

terraform state rm 'fastly_service_v1.<your_resource_name>'
terraform import 'fastly_service_vcl.<your_resource_name>' <service_id>

It's also recommended that you keep a backup of your state file so you can use it to reference any resource IDs necessary.

Logging resources have consistent naming format:

All logging resources now have a consistent naming convention with the provider prefixed with logging_.

• bigquerylogging -> logging_bigquery
• blobstoragelogging -> logging_blobstorage
• gcslogging -> logging_gcs
• httpslogging -> logging_https
• logentries -> logging_logentries
• papertrail -> logging_papertrail
• s3logging -> logging_s3
• splunk -> logging_splunk
• sumologic -> logging_sumologic
• syslog -> logging_syslog

Director capacity removed:

The Fastly API never supported the capacity field for a director resource (this was added to the Terraform provider by mistake). Load balancing of director backends is managed by the weight field on each associated backend resource.

GCS Logging field email renamed:

The Fastly API was updated with a new user field to replace email.

Logging format and format_version defaults changed:

Pre-1.0.0 the default values for format and format_version were incorrectly set to an older version 1. All new logging endpoints use the version 2 custom log format by default.

Backend auto_loadbalance default changed:

The Fastly web interface defaults "Auto load balance" to "No". The most common reason for having multiple backends in a single service is to route different paths to different backends, rather than load balance between different origins. The provider pre-1.0.0 defaulted auto_loadbalance to true, which was considered unexpected behaviour. The default is now false.

Gzip content_types and extensions type changed:

The content_types and extensions fields for a gzip resource, pre-1.0.0, were implemented as a TypeSet (an unordered collection of items whose state index is calculated by the hash of the attributes of the set). This would result in confusing and unexpected diffs. Now they are implemented as a TypeList (an ordered collection of items).

Automatically opt-in to ignore_changes behaviour for versionless resources:

The versionless resources (ACL entries, Dictionary items and Dynamic VCL Snippets) are sometimes used in a way whereby they are "seeded" via Terraform and then updated/managed externally via the API or UI console. For this, the documentation suggests using ignore_changes, a built-in Terraform meta-argument, that allows the user to specify fields to ignore and from which to allow the state to drift.

However, sometimes this isn't obvious or the user doesn't understand this suggestion until it is too late, and data ends up getting lost. This happens because the user makes changes elsewhere and doesn't use ignore_changes, so Terraform takes action to remove the state drift and deletes their changes. This data is then unrecoverable.

In 1.0.0 the default behaviour of these resources has changed. Terraform now ignores any changes, and only allows the "dangerous" behaviour by explicitly opting in with a manage_* option (e.g. manage_entries, manage_items, manage_snippets depending on the versionless resource).

v0.41.0

0.41.0 (January 21, 2022)

ENHANCEMENTS:

• Add activate attribute support for fastly_service_waf_configuration resource #530
• Support updating TLS subscriptions in pending state #528

DOCUMENTATION:

• Revamp fastly_tls_subscription examples #527

v0.40.0

0.40.0 (January 13, 2022)

ENHANCEMENTS:

• Bump go-fastly to v6.0.0 #525
• Add new modsec_rule_ids filter to fastly_waf_rules #521
• Force creation of new condition if type changed #518

DOCUMENTATION:

• Simplify example in fastly_tls_subscription #516
• Update VCL snippet type description #519

v0.39.0

0.39.0 (December 8, 2021)

ENHANCEMENTS:

• Bump go-fastly to v5.1.3 #511
• Expose certificate_id read-only attribute from fastly_tls_subscription #506
• Dynamically generate provider version #500

BUG FIXES:

• Fix constants formatting #504
• Remove -i flag from go test #503

DOCUMENTATION:

• Consistent description for attributes using constants #502
• Update RELEASE.md #499

v0.38.0

0.38.0 (November 5, 2021)

BUG FIXES:

• Do not send 0 subnet value unless explicitly set #496

DOCUMENTATION:

• Utilise codefile and tffile functions from tfplugindocs #497

v0.37.0

0.37.0 (November 1, 2021)

BUG FIXES:

• Ignore 404 on GetPackage when importing wasm service #487
• Properly set IdleConnTimeout to prevent resource exhaustion on tests #491

ENHANCEMENTS:

• Remove TLS subscriptions that 404 from state #479
• Override Transport to enable keepalive and add new force_http2 provider option #485
• Rename GNUmakefile to Makefile #483
• Only update service name and comment if activate is true #481
• Add use_tls attribute for Splunk logging #482

DOCUMENTATION:

• Convert index.md to template to inject provider version #492

v0.36.0

0.36.0 (September 27, 2021)

BUG FIXES:

• Bump go-fastly to v5 to fix API client bugs #477
• Update terraform-json dependency so test suite runs successfully with Terraform v1 #474

ENHANCEMENTS:

• Add support for stale-if-error #475

DOCUMENTATION:

• Clarify edge private dictionary usage #472
• Correct ACL typos #473

v0.35.0

0.35.0 (September 15, 2021)

ENHANCEMENTS:

• Make backend block optional #457
• Audit sensitive attributes #458
• Tests should not error when no backends defined (now considered as warning) #462
• Refactor service attribute handlers into CRUD-style functions #463
• Change to accept multi-pem blocks #469
• Bump go-fastly version #467

BUG FIXES:

• Fix fastly_service_waf_configuration not updating rule attributes correctly #464
• Correctly update version_comment #466

DEPRECATED:

• Deprecate geo_headers attribute #456