Just wanted to clarify here, as I mentioned this in a previous post: How to inform built-in platform plugin that my file type is not theirs - #4 by Nicholas_Hubbard
I already use FileTypeOverrider, but no matter what I do, the Kubernetes plugin sees our YAML files (that my plugin claims, because I don’t have a custom YAML parser) and tacks a bunch of errors and warnings onto them, causing loads of exceptions from my plugin. Because I know that some of the engineers at my company will report this error to me if I don’t do anything to stop it, I immediately warn the user that they need to disable it and offer them an automated method using PluginManagerCore to disable the plugin.
I would definitely appreciate using Plugin Conflicts system when it appears! Until then, I’ll keep using PluginManagerCore, because this isn’t a public plugin.
We also don’t need the Kubernetes plugin in the first place; we have our own customized abstraction layer over it that enforces all of our company policies and rules while abstracting the underlying complexity of Helm charts away from us.