archive_related_authorize? doesn't exist anymore, how do I replace this behavior?
I'm getting forbidden policy checks on a cascading soft destroy.
5 Replies
WDYM it doesn't exist anymore?
we just added it didn't we?
Yes sorry @ZachDaniel I actually misinterpreted the situation.
I saw it was covered in the docs so I assumed it was it the latest version but since it's not, I thought it was removed.
But it's actually not released yet because ash-archival 2.0 isn't released yet, right?
but in < 2.0 related archivals shouldn't need to pass policy checks right ? I'm confused.
Solution
Ah, okay, I didn't realize we hadn't shipped 2.0
I'll ship it now
Just upgrade and set that to
false and you're good to go 😄Ah cool Zach, thanks !