https://pulumi.com
Join Slack
pulumi CLI is behaving strangely for me. It appears to think I am not in an interactive shell. Is th...
# getting-started
l
pulumi CLI is behaving strangely for me. It appears to think I am not in an interactive shell. Is there a variable or something that needs to be set to tell it that I am in an interactive shell?
Some details: I'm using 
fish
shell with 
kitty
terminal. The TERM variable is 
xterm-kitty
l
Try setting TERM to `xterm-256color`: if that works, then raise a bug against https://github.com/pulumi/pulumi
l
That fails as well 😕
Copy code
$ TERM=xterm-256color pulumi up
error: --yes or --skip-preview must be passed in to proceed when running in non-interactive mode
I've also tried running it in gnome terminal and with bash. No luck unfortunately. I will file a bug in the repo.
l
What does 
echo $-
show? Does it include 
i
?
If it doesn't, the you need to raise the bug against kitty, not Pulumi.
(Or maybe fish.. can't be sure)
l
In bash it does:
Copy code
$ echo $-
himBHs
I'm not sure what the corollary is in fish. Maybe:
Copy code
$ status is-interactive && echo true || echo false
true
Oh
Fish says it isn't a login shell 🤔
Copy code
$ status
This is not a login shell
Job control: Only on interactive jobs
I forced a login shell but that didn't change anything.
This isn't a huge deal for now, but it limits my ability to preview changes. 🤷
l
It's very odd
l
Hmm... This worked:
Copy code
$ # Run fish with clean environment
$ env -i fish --no-config
$ pulumi up
Previewing update (dev)
...
There must be some configuration thing happening.
It turned out to be the 
JENKINS_URL
environment variable I was using. Gee whiz! I'm solving the problem by setting 
PULUMI_DISABLE_CI_DETECTION
in my shell. Thanks for the help @little-cartoon-10569 https://github.com/pulumi/pulumi/issues/17863#issuecomment-2501373705
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by