Code completion interactions with the Pulumi YAML LSP server

Hey folks! First I want to say, awesome work on schematizing and providing great completions for YAML documents. It's a great extension.

Background

The Pulumi team is working on an LSP server for our domain specific language, Pulumi YAML, for which static shipped schemas are not the right approach. For context, each YAML program can use multiple resource providers at distinct versions, each of which supports returning its own schema. Our Azure schemas weigh around 100MiB for each version, and that's just one provider!

Accordingly, we've been investing in an LSP server catering to our language & our simple expression language.

What's not working

When a user has both the Red Hat YAML and Pulumi YAML LSP extensions installed, code completions misbehave - double completing or editing the document in "incorrect" ways.

Solutions

I think if we could exclude "Pulumi.yaml" files from your LSP server's activations, or have the Red Hat plugin not serve files if it detects (I am unsure how) that the Pulumi YAML LSP is active for Pulumi.yaml files we might resolve the issue.

No specific files or tests are named. Start by reproducing completion behavior with both the Red Hat YAML and Pulumi YAML LSP extensions installed, then inspect how Pulumi.yaml files are activated and served; done means completions no longer double-apply or edit the document incorrectly.