This message was deleted.
# azures
sparse-intern-71089
04/12/2021, 10:02 PMThis message was deleted.
p
purple-train-14007
04/12/2021, 10:03 PMAh ok. It doesn’t even accept the storage key for me so instead I’m using the SAS token.
b
broad-dog-22463
04/12/2021, 10:03 PMit needs STOAKGE_ACCOUNT AND STORAGE_KEY
broad-dog-22463
04/12/2021, 10:04 PMso that sounds super broken for you then 😕
broad-dog-22463
04/12/2021, 10:04 PMI will get back to it asap!
broad-dog-22463
04/12/2021, 10:04 PMI am working on the last parts for the 3.0-beta.3
p
purple-train-14007
04/12/2021, 10:04 PMYeah, using the storage_key env var give access denied.
purple-train-14007
04/12/2021, 10:05 PMThanks a lot Paul. I think I have the current GA version you guys released.
b
broad-dog-22463
04/12/2021, 10:05 PMyeah I am trying to track down the bug
broad-dog-22463
04/12/2021, 10:05 PMit's somewhere between us, google/go-cloud ad the azure-storage-sdk
broad-dog-22463
04/12/2021, 10:06 PMp
purple-train-14007
04/12/2021, 10:08 PMI would suspect the problem to be google/go-cloud. Azure Storage APIs (im assuming here) shouldn’t care as long as the token is valid. My thoughts is maybe the something in google/go-cloud is modifying the token in a way that azure storage api is rejecting it
purple-train-14007
04/12/2021, 10:08 PMI’ve seen this happen in AD with kerb tokens
3 Views