One thing I noticed about Permit’s EU migration is...
# general
g
One thing I noticed about Permit’s EU migration is that it may involve more than changing an API hostname. There are separate endpoints involved across the SDK, PDP, and SCIM/identity-provider setup. I'm curious how people are checking that they've updated everything across their integration, especially when those settings are spread across different parts of the application. Is there a straightforward way you're verifying this, or are you checking each part separately?
o
It’s basically just the sub domain change. It’s a very easy Search and Replace, especially in the AI era. All customers migrated with ease weeks ago.
g
Got it, thanks for clarifying. I was looking at the different endpoints and assumed the migration might involve more steps than it actually did. Good to know it was straightforward for customers.
The change to how Check handles errors in v1.3.0 caught my attention. Previously, an unhandled PDP response could result in false with no error. Now it can return an error instead. For anyone upgrading, how are you handling that distinction in your application? Do you already handle authorization denials and check errors separately, or does this change require adjustments to your error handling?
o
I think you are confusing some topics here. This is a minor version with a breaking change, and yes now it does throw exceptions.
z
a failed check should error (429 for example)
g
Ah, I see what you mean. I was asking about how applications handle the change from a failed check returning "false" to returning an error. Thanks for clarifying the nature of the change.