The `flux check` is too aggressive about vscode-gitops-tools HOT 3 CLOSED

It looks as though flux check --pre was originally scoped to run only on extension init:

#35

I think we're running it a lot more than that now, on every cluster swap. I've wrapped almost every call to flux check in a boolean and now it looks like they're effectively blocked, but there are a couple of UI elements that don't jibe well against that (you click and there's no feedback, because it would have ran flux check before...)

I'm not going to try to make this perfect for the prerelease, I just want to verify it works locally and then verify it works for you so that you can get on with your work, then we'll work out the details prior to a next mainline release.

Hope this helps

from vscode-gitops-tools.

#238 (comment)

Great reference for "never show again" widgets in another issue here

from vscode-gitops-tools.

There is a pair of configuration widgets in the Gitops Tools preferences now, you can disable the flux check and disable emitting debug messages if you don't wish to see errors anymore.

The flux check configuration is left as the default because those errors you want users to see, they represent something wrong that the user or the platform admin team should address and fix. But if they're known issues, we shouldn't bug the user every time.

Mentioned in the v0.25.1 changelog:

• Allow users to disable running flux check in GitOps Tools preferences

from vscode-gitops-tools.