Hello everyone 👋 . Is it reasonable to use resource scopes as DDD-like “bounded contexts”? i.e. each microservice has its own scope so that resources with the same name (but different meaning) can exist within each?
09/20/2022, 8:07 AM
Yes, you can do that. You could also use the
field in the policies to achieve the same thing.
09/20/2022, 8:17 AM
so the version field could be
I guess the context could be included in the resource name too
09/20/2022, 8:24 AM
I think the
can be just
and you can just call the resource
. So, in effect you are asking Cerbos what a user can do with the