Checking deep in our backend code, the checks need to consider essential snaps as part of any store.
Separately, the help for `snap download` should be extended to say that any user with store viewer role can access snaps by revision if the snap is available from their store.
We got a customer report saying that they couldn't access snapd revision 13640 by using a command like this one:
UBUNTU_ STORE_ID= brand-store- id UBUNTU_ STORE_AUTH_ DATA_FILENAME= store-viewer. credentials snap download --revision=13640 snapd
I investigated further and the snap store ACL API endpoint was returning "false" for "allowed_ by_revision" :
{ external_ id": "usso:https:/ /login. ubuntu. com/+id/ openid- suffix",
"PMrrV4ml8uWuE UDBT8dSGnKUYbev Vhc4": {
"allowed_ if_private" : false,
"allowed_ by_revision" : false
"user_
"permissions": {
}
}
}
Checking deep in our backend code, the checks need to consider essential snaps as part of any store.
Separately, the help for `snap download` should be extended to say that any user with store viewer role can access snaps by revision if the snap is available from their store.