chore(deps): update terraform bunnynet to ~> 0.11 #50

Merged

automation-bot merged 1 commit from renovate/bunnynet-0.x into main 2025-12-20 00:01:55 +00:00

Conversation 0 Commits 1 Files changed 2 +39 -39

automation-bot commented 2025-12-20 00:01:53 +00:00

Owner

• Copy link
• Copy Markdown

This PR contains the following updates:

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

---

Release Notes

BunnyWay/terraform-provider-bunnynet (bunnynet)

v0.11.4

Compare Source

Added

• data source pullzone: allow references by either id or name;

Fixed

• resource pullzone: change default for websockets_enabled;

v0.11.3

Compare Source

Added

• resource dns_zone: expose dnssec_public_key (#​57);
• data source dns_zone: expose dnssec_public_key (#​57);

v0.11.2

Compare Source

Added

• resource dns_zone: support DNSSEC;

Fixed

• resource dns_record: validate weight for type Redirect (#​29)

v0.11.1

Compare Source

Added

• resource dns_record: validate trailing dots on hostname values (#​48);
• resource pullzone_edgerule: document triggers[].type accepted values;

Fixed

• resource dns_record: validate pullzone_id;

v0.11.0

Compare Source

Backwards compatibility break

The resource compute_container_app now uses a list type to define container, endpoint and env blocks. While both set and list types are compatible at the state level, this change has some limitations:

Limitations

• container, endpoint and env blocks have to sorted by name. You'll need to follow the same order on your .tf files, otherwise terraform will show them as modified after an apply;
• Renaming a container, endpoint or env will cause the plan to show unrelated items being modified, as their order jumps up or down. We recommend deleting the block, applying, and then adding the block again with the new name;
• Renaming an endpoint of type CDN might cause pullzones to be recreated, even if they aren't directly affected;

Upgrade path

1. Make sure terraform plan reports no changes;
2. Upgrade the bunny.net provider;
3. Sort the container, endpoint and env blocks in your .tf files;
4. Add version = 2 to your bunnynet_compute_container_app resources;
5. Run terraform plan, it should report no changes apart from the version attribute;

Motivation

While the set type would be the semantically correct type to use for those blocks, Terraform's implementation is neither complete nor uses the same internal details as the List type. This means that changing attributes in a sub-block often causes the entire container to be replaced, causing endpoints to be re-created, including their pullzones. It is also not possible to reference set objects in lifecycle.ignore_changes.

Related issues: #​777, #​974, #​1036.

Changed

• resource compute_container_app: replace Set with List types;
• Bumped minimum Go version to 1.24;
• Bumped minimum Terraform version to 1.5;

v0.10.6

Compare Source

Fixed

• resource pullzone_hostname: allow deletion of bunny.run subdomains (#​54);

---

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.10` -> `~> 0.11` | --- ### Release Notes <details> <summary>BunnyWay/terraform-provider-bunnynet (bunnynet)</summary> ### [`v0.11.4`](https://github.com/BunnyWay/terraform-provider-bunnynet/blob/HEAD/CHANGELOG.md#0114---2025-12-12) [Compare Source](https://github.com/BunnyWay/terraform-provider-bunnynet/compare/v0.11.3...v0.11.4) ##### Added - data source pullzone: allow references by either `id` or `name`; ##### Fixed - resource pullzone: change default for websockets\_enabled; ### [`v0.11.3`](https://github.com/BunnyWay/terraform-provider-bunnynet/blob/HEAD/CHANGELOG.md#0113---2025-11-24) [Compare Source](https://github.com/BunnyWay/terraform-provider-bunnynet/compare/v0.11.2...v0.11.3) ##### Added - resource dns\_zone: expose `dnssec_public_key` ([#&#8203;57](https://github.com/BunnyWay/terraform-provider-bunnynet/pull/57)); - data source dns\_zone: expose `dnssec_public_key` ([#&#8203;57](https://github.com/BunnyWay/terraform-provider-bunnynet/pull/57)); ### [`v0.11.2`](https://github.com/BunnyWay/terraform-provider-bunnynet/blob/HEAD/CHANGELOG.md#0112---2025-11-20) [Compare Source](https://github.com/BunnyWay/terraform-provider-bunnynet/compare/v0.11.1...v0.11.2) ##### Added - resource dns\_zone: support DNSSEC; ##### Fixed - resource dns\_record: validate weight for type Redirect ([#&#8203;29](https://github.com/BunnyWay/terraform-provider-bunnynet/issues/29#issuecomment-3549960461)) ### [`v0.11.1`](https://github.com/BunnyWay/terraform-provider-bunnynet/blob/HEAD/CHANGELOG.md#0111---2025-11-11) [Compare Source](https://github.com/BunnyWay/terraform-provider-bunnynet/compare/v0.11.0...v0.11.1) ##### Added - resource dns\_record: validate trailing dots on hostname values ([#&#8203;48](https://github.com/BunnyWay/terraform-provider-bunnynet/issues/48)); - resource pullzone\_edgerule: document `triggers[].type` accepted values; ##### Fixed - resource dns\_record: validate pullzone\_id; ### [`v0.11.0`](https://github.com/BunnyWay/terraform-provider-bunnynet/blob/HEAD/CHANGELOG.md#0110---2025-10-27) [Compare Source](https://github.com/BunnyWay/terraform-provider-bunnynet/compare/v0.10.6...v0.11.0) ##### Backwards compatibility break The resource `compute_container_app` now uses a [list type](https://developer.hashicorp.com/terraform/plugin/framework/handling-data/types/list) to define `container`, `endpoint` and `env` blocks. While both set and list types are compatible at the [state](https://developer.hashicorp.com/terraform/language/state) level, this change has some limitations: ##### Limitations - `container`, `endpoint` and `env` blocks have to sorted by `name`. You'll need to follow the same order on your .tf files, otherwise terraform will show them as modified after an `apply`; - Renaming a `container`, `endpoint` or `env` will cause the plan to show unrelated items being modified, as their order jumps up or down. We recommend deleting the block, applying, and then adding the block again with the new name; - Renaming an `endpoint` of type CDN might cause pullzones to be recreated, even if they aren't directly affected; ##### Upgrade path 1. Make sure `terraform plan` reports no changes; 2. Upgrade the bunny.net provider; 3. Sort the `container`, `endpoint` and `env` blocks in your .tf files; 4. Add `version = 2` to your `bunnynet_compute_container_app` resources; 5. Run `terraform plan`, it should report no changes apart from the `version` attribute; ##### Motivation While the [set type](https://developer.hashicorp.com/terraform/plugin/framework/handling-data/types/set) would be the semantically correct type to use for those blocks, Terraform's implementation is neither complete nor uses the same internal details as the List type. This means that changing attributes in a sub-block often causes the entire `container` to be replaced, causing endpoints to be re-created, including their pullzones. It is also not possible to reference set objects in `lifecycle.ignore_changes`. Related issues: [#&#8203;777](https://github.com/hashicorp/terraform-plugin-framework/issues/777), [#&#8203;974](https://github.com/hashicorp/terraform-plugin-framework/issues/974), [#&#8203;1036](https://github.com/hashicorp/terraform-plugin-framework/issues/1036). ##### Changed - resource compute\_container\_app: replace Set with List types; - Bumped minimum Go version to 1.24; - Bumped minimum Terraform version to 1.5; ### [`v0.10.6`](https://github.com/BunnyWay/terraform-provider-bunnynet/blob/HEAD/CHANGELOG.md#0106---2025-10-20) [Compare Source](https://github.com/BunnyWay/terraform-provider-bunnynet/compare/v0.10.5...v0.10.6) ##### Fixed - resource pullzone\_hostname: allow deletion of `bunny.run` subdomains ([#&#8203;54](https://github.com/BunnyWay/terraform-provider-bunnynet/issues/54)); </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-->

automation-bot added 1 commit 2025-12-20 00:01:53 +00:00

chore(deps): update terraform bunnynet to ~> 0.11 31ecac8c60

automation-bot scheduled this pull request to auto merge when all checks succeed 2025-12-20 00:01:54 +00:00

automation-bot merged commit 31ecac8c60 into main 2025-12-20 00:01:55 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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!50

No description provided.