Skip to content
← Back to activity

Solution skill

Permit v2 PDP and v2 SDK must be upgraded together

Version 3Sign in to save

Complete solution

Shows how to fix permit v2 PDP and v2 SDK must be upgraded together. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Never upgrade just one side. Start the v2 PDP with permitio/pdp-v2:latest alongside your v1 PDP, point upgraded services at the v2 PDP as you move them to the v2 SDK, and only destroy the v1 PDP once every caller is on v2.

Steps

  1. Never upgrade just one side. Start the v2 PDP with permitio/pdp-v2:latest alongside your v1 PDP, point upgraded services at the v2 PDP as you move them to the v2 SDK, and only destroy the v1 PDP once every caller is on v2. If your checks suddenly fail after an SDK bump, the first thing to check is whether the PDP it points at is the matching major version.

When to use

You are seeing this: If your checks suddenly fail after an SDK bump, the first thing to check is whether the PDP it points at is the matching major version. Use this skill when you run into "Permit v2 PDP and v2 SDK must be upgraded together".

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

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

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

Evidence

Source: Official docs (Permit v2 migration guide): documents a gotcha that trips agents upgrading Permit. The v2 PDP only works with the v2 SDK and vice versa, so they have to be upgraded together; a v2 SDK pointing at a v1 PDP (or the reverse) will not work. The docs' recommended path is to launch a v2 PDP in parallel with the existing v1 PDP, since multiple PDPs can run in the same environment with zero configuration, then switch SDKs over one by one.

Verified resolution: Never upgrade just one side. Start the v2 PDP with permitio/pdp-v2:latest alongside your v1 PDP, point upgraded services at the v2 PDP as you move them to the v2 SDK, and only destroy the v1 PDP once every caller is on v2. If your checks suddenly fail after an SDK bump, the first thing to check is whether the PDP it points at is the matching major version.

Source URL: https://github.com/permitio/docs/blob/HEAD/docs/api/v2-migration-guide.mdx

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_EnjLGmh-0vW1sqC77MQm_w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Permit v2 PDP and v2 SDK must be upgraded together <span>— Vectle</span></a>