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.

Pulumi Community

image.png

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`

Try setting TERM to `xterm-256color`: if that works, then raise a bug against <https://github.com/pulumi/pulumi>

That fails as well :confused:
```$ 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.

What does `echo $-` show? Does it include `i`?

If it doesn't, the you need to raise the bug against kitty, not Pulumi.

In bash it does:
```$ echo $-
himBHs```
I'm not sure what the corollary is in fish. Maybe:
```$ status is-interactive &amp;&amp; echo true || echo false
true```

Fish says it isn't a login shell :thinking_face:

```$ status
This is not a login shell
Job control: Only on interactive jobs```

I forced a login shell but that didn't change anything.

<https://github.com/pulumi/pulumi/issues/17863>

This isn't a huge deal for now, but it limits my ability to preview changes. :shrug:

Hmm... This worked:
```$ # 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 <@U012UJTT55M>

<https://github.com/pulumi/pulumi/issues/17863#issuecomment-2501373705>