Andrew Haines
Andrew Haines
Hi @mdugue! Being able to generate "smarter" clients from your actual policies and schemas is definitely a use case we are interested in supporting, but isn't likely to be implemented...
That wouldn't work for us, unfortunately. We have short-lived access tokens stored in the user's session cookie and we need to refresh those and update the cookie, which requires some...
We ran into a similar case with a redirect response stub in a resource route: https://github.com/remix-run/remix/pull/9479
No problem! Thanks for the suggestion 🙂 Closely related: I'm also introducing reusable groups of principal and resource fixtures in https://github.com/cerbos/cerbos/pull/2340. Hopefully that makes it even easier to write tests!
Related: https://github.com/ajv-validator/ajv-cli/pull/200
Awesome, thanks @timostamm!
I don't understand this one. As it says in [the docs](https://docs.cerbos.dev/cerbos/latest/configuration/engine.html#lenient_scopes) > This setting only affects how Cerbos treats missing leaf scopes when searching for policies. How could we know...
Ok, that makes more sense. So maybe we can do something like "If a test fails, but would've passed had `lenientScopeSearch` been enabled, include a warning in the results"?
I would be reluctant to print a message if everything is fine, except maybe in verbose mode.
Nice, that sounds good to me!