https://pulumi.com logo
Title
b

brash-gigabyte-81569

11/07/2022, 5:15 PM
Had a weird issue and I am not sure if it is related to deployments 🧵
Basically we had a stack that we were managing manually and then we tested out deployments with it
and after that I wasn’t able to delete the stack as it didn’t seem to be able to get the credentials for the one provider
tried refreshing, up’ing, and destroying and all failed as though the creds for the provider werent making it to it
b

brainy-church-78120

11/07/2022, 5:54 PM
@brash-gigabyte-81569 did the deployment you tried succeed?
b

brash-gigabyte-81569

11/07/2022, 5:55 PM
no they did not
b

brainy-church-78120

11/07/2022, 5:56 PM
are they also failing on creds errors? if so, can you try adding the creds as environment variables in stack settings > deploy?
b

brash-gigabyte-81569

11/07/2022, 5:56 PM
no they had failed due to character limit on the directories
I am not seeing env vars section in the stack settings
b

brainy-church-78120

11/07/2022, 5:58 PM
do you see a deploy section in the left nav when you go to stack settings? could you dm me a screenshot of what you see on that page?
r

red-match-15116

11/07/2022, 6:10 PM
tried refreshing, up’ing, and destroying and all failed as though the creds for the provider werent making it to it
You tried all this using the CLI/manually or was this all failing in deployments?
b

brash-gigabyte-81569

11/07/2022, 6:11 PM
yes all in the CLI
Going to attempt clearing the deployment
r

red-match-15116

11/07/2022, 6:13 PM
yes all in the CLI
that is super odd! I wouldn't expect this to be related to deployments... and you're sure you have valid creds in your env? (sorry for the obvious question!)
b

brash-gigabyte-81569

11/07/2022, 6:15 PM
All good, feel free to probe. I got on with support for the provider to confirm credentials on Friday
and I was able to use their CLI with the creds without issue
r

red-match-15116

11/07/2022, 6:16 PM
can you create a different stack with the same creds?
b

brash-gigabyte-81569

11/07/2022, 6:16 PM
Only 2 things we changed from when it was working to not working was I updated the pulumi cli from 3.43.1 to 3.46.0 and we tried out deployments
r

red-match-15116

11/07/2022, 6:18 PM
I think to help narrow down if this is specific to this stack I would try creating a different arbitrary stack with a resource from this provider and see if it still works. And I would also confirm if maybe there was a new provider version if you don't have it pinned?
b

brash-gigabyte-81569

11/07/2022, 6:20 PM
yeah i can try creating a new stack and see if i can destroy it
i did confirm that the provider hasn’t changed
r

red-match-15116

11/07/2022, 6:20 PM
I guess while I wouldn't eliminate the possibility that it's deployments I would find that extremely surprising since: 1) you weren't actually able to completely set up deployments 2) deployments don't effect anything about the CLI path, just offer a separate environment to run. would be awesome to figure out if we've missed something though!
b

brash-gigabyte-81569

11/07/2022, 6:22 PM
Yeah, I did note some changes in pulumi around config handling so tried using an older version, not sure if i did it right now since it saw it still hitting files in the ~/.pulumi/plugins
I think i confirmed it is an issue with the latest pulumi cli
i downgraded to 3.43.1 for pulumi and pulumi-language-go and it worked
(i tried this on friday but only changed on the pulumi bin, today i also changed out the pulumi-language-go)