chore(deps): update terraform bunnynet to ~> 0.12 #53
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/bunnynet-0.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
~> 0.11->~> 0.12Release Notes
BunnyWay/terraform-provider-bunnynet (bunnynet)
v0.12.0Compare Source
Backwards compatibility break
The
transformationsattribute in bothpullzone_ratelimit_ruleandpullzone_waf_ruleresources was moved from theconditionblock to the resource itself. This was done in order to accommodate multipleconditionblocks, although you can only apply transformations on a per-resource basis.This means that for a resource like the example below, both
LOWERCASEandNORMALIZEPATHwill apply to both conditions:Added multiple
conditionsupportBoth
pullzone_ratelimit_ruleandpullzone_waf_rulenow support multipleconditionblocks. There are a few limitations though:conditionblocks have to sorted byvariable. You'll need to follow the same order on your .tf files, otherwise terraform will show them as modified after anapply;variablewill 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
conditionblocks;conditionblocks;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.
This PR has been generated by Renovate Bot.