You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a demand for public containers that are free for writing but are locked for deleting. Users tend to use well-known public-read-write basic ACL, but it requires restrictive extended ACL with a bearer token control of the user actions. It's a bit complicated for the newcomers.
Instead I propose to define public-append basic ACL constant. Container owner stays in charge of the data control, but other users cannot delete any objects, so data won't be lost "accidentally".
There is a demand for public containers that are free for writing but are locked for deleting. Users tend to use well-known
public-read-write
basic ACL, but it requires restrictive extended ACL with a bearer token control of the user actions. It's a bit complicated for the newcomers.Instead I propose to define
public-append
basic ACL constant. Container owner stays in charge of the data control, but other users cannot delete any objects, so data won't be lost "accidentally".I am not sure whether bearer token bit should be set for DELETE or not.
This change should be reflected in neofs-spec.
/cc @realloc @cthulhu-rider @carpawell
The text was updated successfully, but these errors were encountered: