Is there any plans to decrease the scope of what R2 API tokens have access to? Currently: * There a
Is there any plans to decrease the scope of what R2 API tokens have access to? Currently:
- There are two access levels, read, or write, any consideration to make this more granular? What if my token only needs to Put items, but does not need to Delete anything? (protecting from mass deletion attacks)
- Allowing us to scope what buckets each token has access to, I host a few R2 buckets, and a lot of them have to write to their relevant R2 bucket, it would be neat if I could scope them to be able to only write to the buckets they actually need.
