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
We have been using Azure Blog Storage with SAS tokens for authentication so far. That's ok for maintainers but how we can give read access to everybody. I think we should have a basic installation like this:
It seems you can change the access level of the container:
but I would prefer to create a token with read-only permissions if possible because that way we could even control who has read access. People could ask for a read-only token. But anyway it seems once you generate one SAS token there is no way to revoke it: https://docs.microsoft.com/en-us/azure/storage/common/storage-sas-overview#best-practices-when-using-sas or I least, I do not find any option to list them and revoke them manually.
We have been using Azure Blog Storage with SAS tokens for authentication so far. That's ok for maintainers but how we can give read access to everybody. I think we should have a basic installation like this:
I tried to generate a read-only SAS token:
but it does not work. I was able to push new images with dvc push.
I have opened a topic on the DVC community: https://discuss.dvc.org/t/read-only-access-using-azure-blog-storage/910
I think it should be possible.
Official docs: https://docs.microsoft.com/en-us/rest/api/storageservices/create-service-sas#ad-hoc-sas-versus-stored-access-policy
The text was updated successfully, but these errors were encountered: