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
This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
stalebot
added
the
stale
A stale issue or PR that will automatically be closed.
label
Mar 19, 2021
Hi, just here to add my voice to the fact that this is indeed an anticipated feature !
I am working with an Azure reseller that only allows Shared Access Signatures and I am therefore unable to use Loki in that context.
This thanos-io/objstore#52 would need to move forward first, then I could submit a PR for loki to utilize it. It is a niche use case, but adding to the discussion on the issue and PR could help move it forward.
Describe the bug
When using Azure Blob SAS token instead of Account Key, Loki throws this error:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Loki should accept SAS token
Environment:
Kubernetes 1.16.13
Helm 3.5.1
Loki works with Azure Blob Account Keys, but they are not recommended due to very wide permissions
The text was updated successfully, but these errors were encountered: