Refresh the schema for a loaded document

I have a situation where:

• I need to fetch schemas from a remote location
• Schemas can change when updates are deployed to the remote location

(Specifically, the environment is Kubernetes custom resource definitions, where the schemas in a cluster depend on what CRDs are deployed, and a CRD schema can change when the CRD is updated.)

My current approach is to have a fallback schema while I wait for the actual schemas to download, and to fetch new schemas when I detect changes that could affect the schema. This works fine for documents that are loaded after I have received the schemas.

But for documents that are already open at extension startup, vscode-yaml asks me for a schema when I only have the fallback one. And when I receive the real one I can't see a way to tell it "hey, I now have a better schema, can you use this one / ask me again please." Similarly, if someone opens a custom resource YAML document, then updates the schema for the custom resource definition, I can't tell vscode-yaml "hey, the schema for this document has changed, can you use this one instead, and recalculate validations and code completions etc."

Would it be possible to add a way to tell vscode-yaml to re-request the content of an existing schema, or to re-request the schema for an existing resource? Or would you recommend another way of tackling my scenario?

Please let me know if I can clarify this request in any way!

No files, tests, or entry points are named. Start by tracing how vscode-yaml requests schemas and applies them to already-open documents, then determine how schema refreshes should trigger validation and completion updates. Done means the extension can re-request or replace a schema for an existing document and recalculate its language features.