deislabs
Access policy for a bindle?
Has any thought been given to access policy for a bindle?
/_i/{bindle-name}@{parcel-id}
I'm really glad that all parcel fetches are done in the context of a bindle name. This means that the invoice can define access control for both itself and its parcels. A user, for example, should be able to always fetch their own bindles. But they should also allow fetching of bindles selectively for other users (or even other criteria). The access policy for a bindle should include the invoice itself. For example, if a user doesn't have access to a bindle it cannot see either the invoice or any of the parcels.
This is definitely something we've thought through (see the Authorizable and Authorizer traits), but we haven't implemented this yet. I do have an initial design written up in a HackMD somewhere. Let me grab the relevant info and open up a new issue with it
