chore(deps): update terraform bunnynet to ~> 0.12 #53

Merged
automation-bot merged 1 commit from renovate/bunnynet-0.x into main 2026-01-30 00:02:19 +00:00
Owner

This PR contains the following updates:

Package Type Update Change
bunnynet (source) required_provider minor ~> 0.11 -> ~> 0.12

Release Notes

BunnyWay/terraform-provider-bunnynet (bunnynet)

v0.12.0

Compare Source

Backwards compatibility break

The transformations attribute in both pullzone_ratelimit_rule and pullzone_waf_rule resources was moved from the condition block to the resource itself. This was done in order to accommodate multiple condition blocks, although you can only apply transformations on a per-resource basis.

This means that for a resource like the example below, both LOWERCASE and NORMALIZEPATH will apply to both conditions:

resource "bunnynet_pullzone_ratelimit_rule" "ratelimit_login_page" {
  # ...
  transformations = ["LOWERCASE", "NORMALIZEPATH"]

  condition {
    variable = "REQUEST_METHOD"
    operator = "STREQ"
    value = "post"
  }

  condition {
    variable = "REQUEST_URI"
    operator = "BEGINSWITH"
    value = "/login"
  }
}
Added multiple condition support

Both pullzone_ratelimit_rule and pullzone_waf_rule now support multiple condition blocks. There are a few limitations though:

  • condition blocks have to sorted by variable. You'll need to follow the same order on your .tf files, otherwise terraform will show them as modified after an apply;
  • Changing a variable will cause the plan to show unrelated conditions being modified, as their order jumps up or down. We recommend deleting the block, applying, and then adding the block again with the new variable name;
Added
  • Support for Database
  • resource compute_container_app: support persistent volumes;
  • resource pullzone_ratelimit_rule: support multiple condition blocks;
  • resource pullzone_waf_rule: support multiple condition blocks;

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC), Automerge - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [bunnynet](https://registry.terraform.io/providers/bunnyway/bunnynet) ([source](https://github.com/BunnyWay/terraform-provider-bunnynet)) | required_provider | minor | `~> 0.11` -> `~> 0.12` | --- ### Release Notes <details> <summary>BunnyWay/terraform-provider-bunnynet (bunnynet)</summary> ### [`v0.12.0`](https://github.com/BunnyWay/terraform-provider-bunnynet/blob/HEAD/CHANGELOG.md#0120---2026-01-29) [Compare Source](https://github.com/BunnyWay/terraform-provider-bunnynet/compare/v0.11.6...v0.12.0) ##### Backwards compatibility break The `transformations` attribute in both `pullzone_ratelimit_rule` and `pullzone_waf_rule` resources was moved from the `condition` block to the resource itself. This was done in order to accommodate multiple `condition` blocks, although you can only apply transformations on a per-resource basis. This means that for a resource like the example below, both `LOWERCASE` and `NORMALIZEPATH` will apply to *both* conditions: ```terraform resource "bunnynet_pullzone_ratelimit_rule" "ratelimit_login_page" { # ... transformations = ["LOWERCASE", "NORMALIZEPATH"] condition { variable = "REQUEST_METHOD" operator = "STREQ" value = "post" } condition { variable = "REQUEST_URI" operator = "BEGINSWITH" value = "/login" } } ``` ##### Added multiple `condition` support Both `pullzone_ratelimit_rule` and `pullzone_waf_rule` now support multiple `condition` blocks. There are a few limitations though: - `condition` blocks have to sorted by `variable`. You'll need to follow the same order on your .tf files, otherwise terraform will show them as modified after an `apply`; - Changing a `variable` will cause the plan to show unrelated conditions being modified, as their order jumps up or down. We recommend deleting the block, applying, and then adding the block again with the new variable name; ##### Added - Support for Database - resource compute\_container\_app: support persistent volumes; - resource pullzone\_ratelimit\_rule: support multiple `condition` blocks; - resource pullzone\_waf\_rule: support multiple `condition` blocks; </details> --- ### Configuration 📅 **Schedule**: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC), Automerge - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNzMuMSIsInVwZGF0ZWRJblZlciI6IjQxLjE3My4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
chore(deps): update terraform bunnynet to ~> 0.12
Some checks failed
ci/crow/cron/update-package-index-redhat-9-amd64 Pipeline failed
ci/crow/cron/update-package-index-alpine-321-amd64 Pipeline was successful
ci/crow/cron/update-package-index-alpine-323-amd64 Pipeline was successful
ci/crow/cron/update-package-index-ubuntu-2204-amd64 Pipeline failed
ci/crow/cron/update-package-index-ubuntu-2204-arm64 Pipeline failed
ci/crow/cron/update-package-index-ubuntu-2404-amd64 Pipeline failed
ci/crow/cron/update-package-index-ubuntu-2404-arm64 Pipeline failed
ci/crow/cron/update-package-index-redhat-9-arm64 Pipeline failed
ci/crow/cron/process-updates-alpine-323-arm64 Pipeline was successful
ci/crow/cron/process-updates-redhat-9-arm64 Pipeline was successful
ci/crow/cron/process-updates-ubuntu-2204-arm64 Pipeline was successful
ci/crow/cron/process-updates-ubuntu-2404-arm64 Pipeline is running
ci/crow/cron/process-updates-alpine-322-arm64 Pipeline was successful
ci/crow/cron/process-updates-redhat-8-arm64 Pipeline was successful
ci/crow/cron/update-package-index-alpine-321-arm64 Pipeline is running
ci/crow/cron/update-package-index-alpine-322-amd64 Pipeline is running
ci/crow/cron/update-package-index-alpine-323-arm64 Pipeline is running
ci/crow/cron/update-package-index-alpine-322-arm64 Pipeline is running
ci/crow/cron/update-package-index-redhat-8-arm64 Pipeline is running
ci/crow/cron/update-package-index-redhat-8-amd64 Pipeline is running
ci/crow/cron/process-updates-ubuntu-2204-amd64 Pipeline is running
ci/crow/cron/process-updates-ubuntu-2404-amd64 Pipeline is running
ci/crow/cron/process-updates-redhat-8-amd64 Pipeline is running
ci/crow/cron/process-updates-alpine-323-amd64 Pipeline is running
ci/crow/cron/process-updates-redhat-9-amd64 Pipeline is running
ci/crow/cron/process-updates-alpine-322-amd64 Pipeline is running
06f2b1b5bc
automation-bot scheduled this pull request to auto merge when all checks succeed 2026-01-30 00:02:18 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
devxy/build-cran-binaries!53
No description provided.