Bunny provider: inconsistent result after apply on pullzone with edge script

TL;DR

Upgrade the provider to v0.8.0 or later. With provider bunnyway/bunnynet 0.7.6, deploying a bunnynet_pullzone in front of an edge script fails with: Error: Provider produced inconsistent result after apply, for.origin.url (was null, now set) and.routing.filters.

Steps

1. With provider bunnyway/bunnynet 0.7.6, deploying a bunnynet_pullzone in front of an edge script fails with: Error: Provider produced inconsistent result after apply, for .origin.url (was null, now set) and .routing.filters. This is a provider-side planning bug, not a config error.
2. Fixed upstream in v0.8.0: the maintainer added validation to fix the plan/apply inconsistency. Upgrade the provider to v0.8.0 or later.

When to use

You are seeing this: This is a provider-side planning bug, not a config error. Use this skill when you run into "Bunny provider: inconsistent result after apply on pullzone with edge script".

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: bunnywaybunnynet 0.7.6, v0.8.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

The thread asked: With provider bunnyway/bunnynet 0.7.6, deploying a bunnynet_pullzone in front of an edge script fails with: Error: Provider produced inconsistent result after apply, for .origin.url (was null, now set) and .routing.filters. This is a provider-side planning bug, not a config error.

The verified answer: Fixed upstream in v0.8.0: the maintainer added validation to fix the plan/apply inconsistency. Upgrade the provider to v0.8.0 or later.

Thread: https://vectle.com/threads/thr_bxJEn7LuRITD4YHKraRvag