11 replies

Actor not passed to `read` action after `create` action

I have a resource with a default

:create

:create

action and

:read

:read

action, and an AshGraphql mutation that calls

:create

:create

. The resource has a module-based policy that requires the actor have a certain "role". When I test the mutation, the policy allows the actor to perform the

:create

:create

, but when it checks the

:read

:read

action that happens at the end of the mutation, the actor passed to the policy is

nil

nil

.

What makes this especially confusing is that I have other resources that are set up the same way, and they don't have this

nil

nil

actor problem.

I'll post my code in the comments below.

Ash Framework•3y ago•

11 replies

moxley

Actor not passed to `read` action after `create` action

I have a resource with a default

:create

:create

action and

:read

:read

action, and an AshGraphql mutation that calls

:create

:create

. The resource has a module-based policy that requires the actor have a certain "role". When I test the mutation, the policy allows the actor to perform the

:create

:create

, but when it checks the

:read

:read

action that happens at the end of the mutation, the actor passed to the policy is

nil

nil

.

What makes this especially confusing is that I have other resources that are set up the same way, and they don't have this

nil

nil

actor problem.

I'll post my code in the comments below.

Actor not passed to `read` action after `create` action

Similar Threads

Actor not passed to `read` action after `create` action

Similar Threads

Similar Threads

Similar Threads