Bunny Terraform provider: pullzone creation fails with invalid Magic Containers App ID

Not specified by the original author.

TL;DR

Upgrade the provider to v0.15.2 or later. Running terraform apply with the Bunny terraform provider (v0.10.3) fails when creating a bunnynet_pullzone for a Magic Containers app with: The Magic Containers App ID is not valid.

Steps

1. Running terraform apply with the Bunny terraform provider (v0.10.3) fails when creating a bunnynet_pullzone for a Magic Containers app with: The Magic Containers App ID is not valid. The pullzone needs the container endpoint ID, which the provider did not expose as a usable value in that version.
2. Fixed in provider v0.15.2: you can now obtain the container endpoint ID directly, so the pullzone origin can reference it without inspecting generated resources. Maintainer rafael-at-bunny shipped the fix and updated the docs with a working example. Upgrade the provider to v0.15.2 or later.

When to use

You are seeing this: The pullzone needs the container endpoint ID, which the provider did not expose as a usable value in that version. Use this skill when you run into "Bunny Terraform provider: pullzone creation fails with invalid Magic Containers App ID".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: v0.10.3, provider v0.15.2. If you are on something much newer or older, the details may have shifted.

Why this happens

Running terraform apply with the Bunny terraform provider (v0.10.3) fails when creating a bunnynet_pullzone for a Magic Containers app with: The Magic Containers App ID is not valid.

In the thread Bunny Terraform provider: pullzone creation fails with invalid Magic Containers App ID, the question was: Running terraform apply with the Bunny terraform provider (v0.10.3) fails when creating a bunnynetpullzone for a Magic Containers app with: The Magic Containers App ID is not valid. The pullzone needs the container endpoint ID, which the provider did not expose as a usable value in that version. The verified resolution: Fixed in provider v0.15.2: you can now obtain the container endpoint ID directly, so the pullzone origin can reference it without inspecting generated resources. Maintainer rafael-at-bunny shipped the fix and updated the docs with a working example. Upgrade the provider to v0.15.2 or later. Original discussion: https://vectle.com/threads/thrrZqvPKZ4FG9omzdavwsIpw