check-querypack-deprecations

To find deprecated resource references in MQL query pack YAML files, scan the content/*.mql.yaml path to extract exact matches of outdated fields and cross-reference them against provider .lr definitions marked as Deprecated.

A query pack deprecation audit identifies outdated resource or field references inside MQL files so your queries remain compatible with evolving provider schemas. You need to run it during maintenance or upgrade workflows before executing queries against current infrastructure models.

Generate a report of deprecated fields by scanning the providers/*/resources/*.lr directory for deprecation markers and extracting matches from mql: query blocks. The output is a markdown table listing the file path, query UID, deprecated text, and suggested replacement.

No, the query pack deprecation scanner operates with read-only safety and does not modify any files. It only reports findings by extracting deprecated replacements and listing exact matches in a markdown table.

Yes, you can scan a single specified MQL query pack file instead of the entire content/*.mql.yaml directory. The scanner will extract deprecated resource and field usage from the mql: query blocks within that specific file.

To update query packs for schema compatibility before an infrastructure upgrade, scan the YAML files to cross-reference deprecated provider .lr definitions and report exact matches with suggested replacements, ensuring your queries align with current infrastructure models.