kalle (jag)

This is not intentional. Thanks for the report!

> I can pick this up if you want @applejag Sure, go for it! :) One thing that's special about this one is that it has different coloring rules for...

Alright, so understand that as "no, because of technical limitation in Nix" But would it be possible to do something like the Nix expression builds like `.flox/pkgs/foobar.nix` but for environment...

I've noticed that setting platformHooks makes this break for older Helm versions. I've had some of my CI/CD systems break from this. So I'd like to not be too eager...

Yeah agreed we should just imply `--plain` in this case. In #65 we hit a similar issue, where then plan is to do some bigger refactorings to still have color...

> I think we will need an env var that will do the same as --plain. [NO_COLOR](https://kubecolor.github.io/reference/environment-variables/#no_color) does this.

> The issue has become more prominent with the newest .kuberc alias feature. Since --plain is kubecolor specific option, it's impossible to use it in the alias. Could you create...

I did not suggest removing the e2e tests. They are very good and should remain. But the point of this issue was that they run and modify my environments when...

Alright we're again getting off topic. Running `make test-e2e` may modify kind clusters from current context, I never suggested otherwise. What I'm saying is that please add Go build tags...

When looking at the latest scaffold from kubebuilder v4.5.1 I do not see any protection against if the user runs `go test ./...`. It seems to still just go ahead...