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

For example, are you seeing no colors, but would like them?

are you seeing control codes printed out, but not colorized?

The issue is probably here: <https://github.com/pulumi/pulumi/blob/6e29ada4b8478b8cc0f1fcf57991b131e21987ed/pkg/util/cmdutil/diag.go#L38-L44>

I would guess that when run as part of CircleCI, we don't believe we are connected to a terminal and so we don't print the color codes.

image.png

`pulumi preview --non-interactive --color always`

that means that pulumi thinks this is *not* a terminal

which would also explain the lack of colors

anything that can be done to override that?

im guessing its not just as simple as setting `TERM` env var

i don't k now enoug about unix+go to know :slightly_smiling_face:

i spelunked through the go code, and this bottoms out in stuff that's really beyond me unfortunately.  Sorry!  Maybe someone else will have an idea.

yeah, that says to just echo raw colorization codes

and really, that value only exists so we can test things :slightly_smiling_face:

i might compile a custom binary just for this

is there anything online about how to get circleci to behave more like a terminal?

<@UB9JVTW07> Is the issue possibly what Matt pointed out? That we are intentionally switching to `color.Never`, due to

```
if globalColorization == colors.Always &amp;&amp; !terminal.IsTerminal(int(os.Stdout.Fd())) {
		return colors.Never
	}
```

? Not sure, but if so, it seems like if someone explicitly asked for colorization, we should respect it?

IMHO, we should bring back the Auto value for colorization (and have it be the default) and update the above to check colors.Auto instead of Always and just respect Always, Never and Raw.

just ran into the same problem on gitlab ci

Opened <https://github.com/pulumi/pulumi/issues/2021> to track this. 

PR open to handle this: <https://github.com/pulumi/pulumi/pull/2023>

If you now pass `--color=always`, we'll respect that and actually print colors no matter what.  Leaving out the command line option, or specifying 'auto' will put us in the mode where we try to figure out what's best in terms or colors or not.