Cached permissions on multiple instances running on Octane / Kubernetes about laravel-permission HOT 12 CLOSED

Okay. I think what we'll do is, in this package add the reset for team ID and wildcard permissions.

And then for the parts you need in your own app, you can register a listener on Octane's OperationTerminated for those things unique to your own requirements.

from laravel-permission.

public function clearPermissionsCollection(): void 
{ 
   $this->permissions = null; 
   $this->wildcardPermissionsIndex = []; 
} 

from laravel-permission.

I've not yet worked with Octane for a production app, so my "testing" of things like this has been limited. But would like to dig deeper.

Do you mind providing a demo app, replicating the features and symptoms you describe, which we can use for exploring and debugging further?

from laravel-permission.

@drbyte, as the current code base relies on many services (realtime events, after role switch), it would be easier to create a simple example with a single controller and a few endpoints to change a role.

I think the best way to test & debug would be an example which runs on a local micrk8s instance. But I would need some time for the example.

from laravel-permission.

$event->sandbox->make(PermissionRegistrar::class)->forgetCachedPermissions();

that removes the cache in each request and create a new one again, if you are going to do that it is better to use array in the cache store configuration, this way you will use less resources

What do you use for the cache? redis?

from laravel-permission.

What do you use for the cache? redis?

I am using redis. I tried a different approach, since I don't want to clear the entire cache:

This also works.

@drbyte, fyi.

from laravel-permission.

Make a PR

from laravel-permission.

I'm not sure it's safe to hard-code any resets to instance of User because we can't guarantee that.
Perhaps instance of Authenticatable contract.

But is the call to $user->resetPermissionDate() critical?

from laravel-permission.

I agree with the call to setPermissionsTeamId(null) and forgetWildcardPermissionIndex().

from laravel-permission.

@drbyte, we are using some custom permission cache on the user - this part can be ignored. Most important seems to be, that the wildcard cache is beeing deleted.

from laravel-permission.

Hmmm ... I forgot: we already have the reset for team ID since 6.1.0

from laravel-permission.

So ... @erikn69 @parallels999 I'm curious your opinion on whether we should add an Octane-specific reset for forgetWildcardPermissionIndex(), or simply combine forgetWildcardPermissionIndex() into clearPermissionsCollection()

Noting:

from laravel-permission.