Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
plugin-framework
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
b
broad-dog-22463
04/12/2021, 10:02 PMIf so, I have an open issue with google/go-cloud upstream - the way to unblock yourself right now is to not use SAS_TOKEN and use STORAGE_KEY instead
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
so that sounds super broken for you then 😕
I will get back to it asap!
I 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.
Thanks 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
it's somewhere between us, google/go-cloud ad the azure-storage-sdk
p
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
I’ve seen this happen in AD with kerb tokens