fix: remove overeager GCP Blueprint Metadata fileMatch - #6046
Merged
hyperupcall merged 1 commit intoJul 20, 2026
Merged
Conversation
The catalog previously matched every `metadata.yaml` and `metadata.display.yaml` in a workspace, which falsely applied the GCP Blueprint schema to unrelated metadata files. Maintainer guidance on SchemaStore#5985 was to remove both fileMatch entries so users can still select the schema manually without automatic false positives. Closes SchemaStore#5985
Solaris-star
requested review from
hyperupcall and
madskristensen
as code owners
July 19, 2026 18:44
Contributor
|
Thanks for the PR! This section of the codebase is owned by @madskristensen and |
Member
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Removes the automatic
fileMatchfor GCP Blueprint Metadata so IDE schema association no longer treats everymetadata.yaml/metadata.display.yamlas a GCP Blueprint.Why
metadata.yamlis an extremely common filename. Matching it globally causes false-positive schema validation for unrelated projects (issue #5985).Maintainer note on the issue: a PR that removes both
fileMatches is welcome / mergeable. Users can still select the schema manually when they are actually editing GCP Blueprint metadata.Change
src/api/json/catalog.json: dropfileMatchfrom theGCP Blueprint Metadatacatalog entry (schema URL unchanged).Closes #5985