v1.0.1

Add comment support to records @glensc (#49)

Simple string value. As record is typed as any, no documentation changes.

🤖 Automatic Updates

Update .github/settings.yml @osterman (#45)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

v1.0.0

feat! remove firewall rules @bcdady (#43)

Remove deprecated filter and firewall resources

what

Support for the following resources, which are deprecated, are removed from this module.

• cloudflare_firewall_rule
• cloudflare_filter

why

Cloudflare converted existing firewall rules into WAF custom rules

The Firewall Rules API and the associated Cloudflare Filters API are now deprecated. These APIs will stop working on 2024-07-01

Relevant changes for Terraform users

The following Terraform resources from the Cloudflare provider are now deprecated:
* cloudflare_firewall_rule
* cloudflare_filter

Removing the functionality from this module, related to the deprecated resources, addresses multiple issues, including indirectly supporting #40 and #20

references

• closes #25

🤖 Automatic Updates

Update release workflow to allow pull-requests: write @osterman (#42)

what

• Update workflow (.github/workflows/release.yaml) to have permission to comment on PR

why

• So we can support commenting on PRs with a link to the release

Update GitHub Workflows to use shared workflows from '.github' repo @osterman (#41)

what

• Update workflows (.github/workflows) to use shared workflows from .github repo

why

• Reduce nested levels of reusable workflows

Update GitHub Workflows to Fix ReviewDog TFLint Action @osterman (#39)

what

• Update workflows (.github/workflows) to add issue: write permission needed by ReviewDog tflint action

why

• The ReviewDog action will comment with line-level suggestions based on linting failures

Update GitHub workflows @osterman (#38)

what

• Update workflows (.github/workflows/settings.yaml)

why

• Support new readme generation workflow.
• Generate banners

Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#36)

what

• Install latest GitHub Action Workflows

why

• Use shared workflows from cldouposse/.github repository
• Simplify management of workflows from centralized hub of configuration

Add GitHub Settings @osterman (#31)

what

• Install a repository config (.github/settings.yaml)

why

• Programmatically manage GitHub repo settings

Update Scaffolding @osterman (#29)

what

• Reran make readme to rebuild README.md from README.yaml
• Migrate to square badges
• Add scaffolding for repo settings and Mergify

why

• Upstream template changed in the .github repo
• Work better with repository rulesets
• Modernize look & feel

v0.5.1

🚀 Enhancements

Bugfix: multiple named types @Benbentwo (#27)

what

Bugfix having multiple records of the same name & type

why

• Bugfix

v0.5.0

Add account_id to allow module to function @JohnShortland (#24)

what

• Added account_id as a variable
• Added account_id to teh record resource

why

• Module no longer worked if creating any records

Planning changes with 0 custom hooks...
Error: Missing required argument
on .terraform/modules/zone/main.tf line 23, in resource "cloudflare_zone" "default":
23: resource "cloudflare_zone" "default" {
The argument "account_id" is required, but no definition was found.
Unexpected exit code when planning changes: 1

references

closes #22

Sync github @max-lobur (#23)

Rebuild github dir from the template

v0.4.0

• No changes

v0.3.0

Update for Nitpicks @milldr (#19)

what

• updated default records
• removed flatten

why

• Fix edge case in #14
• Remove flatten() as it's confusing and unnecessary

references

• Closes #14

v0.2.0

feat: support record.key entries @aldoborrero (#17)

What

• Addition of the possibility of adding an extra key argument to records variable to disambiguate specific scenarios where collisions may occur.
• Addition of extra - to records key generation to better align with rest of the codebase.

Why

• Currently, we can't specify records that may produce the same id but with different values like the example below (which are valid ones):

module "test" {
  source  = "cloudposse/zone/cloudflare"
  version = "0.1.2"

  context            = module.test_label.context
  zone                = "example.com"
  zone_enabled = false
  enabled           = true
  records            = [
   {
      name    = "@"
      priority  = 1
      ttl          = 1
      type      = "MX"
      value    = "a.example.com"
    },
    {
      name     = "@"
      priority   = 5
      ttl           = 1
      type       = "MX"
      value     = "b.example.com"
    },
  ]
}

This PR changes this with the addition of a key resource:

module "test" {
  source  = "cloudposse/zone/cloudflare"
  version = "0.1.2"

  context            = module.test_label.context
  zone                = "example.com"
  zone_enabled = false
  enabled           = true
  records            = [
   {
      key        = "@-MX-1"
      name     = "@"
      priority   = 1
      ttl           = 1
      type       = "MX"
      value     = "a.example.com"
    },
    {
      key        = "@-MX-2"
      name     = "@"
      priority   = 5
      ttl           = 1
      type       = "MX"
      value     = "b.example.com"
    },
  ]
}

The key can be applied optionally to the records that needs them. It doesn't force to define one in all records.

References

• Closes #15

v0.1.2

git.io->cloudposse.tools update @dylanbannon (#5)

what and why

Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References

• DEV-143

🚀 Enhancements

Add `explicit_cache_control`, bump versions, rm deprecations @amotpan (#6)

what

• Add explicit_cache_control to pagerule.tf (thanks to @amotplan)
• Bump versions and remove deprecations (thanks to @toketas)

why

• Whether origin Cache-Control action is "on" or "off".

references

• https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/page_rule#explicit_cache_control
• https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/healthcheck
• Closes #7
• Closes #11
• Related to #8
• Related to #9
• Related to #10

v0.1.1

🤖 Automatic Updates

Update context.tf @cloudpossebot (#4)

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.

v0.1.0

fix: resolve minor typos (#2)