provider-verification

Verify MQL provider schema changes against live cloud infrastructure.

407|38|Updated Aug 16, 2022
One-click install
npx skills add https://github.com/mondoohq/mql --skill provider-verification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: provider-verification
Source: https://github.com/mondoohq/mql/tree/main/.claude/skills/provider-verification
Command: npx skills add https://github.com/mondoohq/mql --skill provider-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of provider schema and field changes that look correct in code but fail or return wrong data only when exercised against live cloud APIs.

Core Features & Use Cases

  • Diff-driven verification: extracts added/changed .lr resources and fields plus affected provider .go files from a PR or commit range.
  • Live, cheapest-infra smoke testing: provisions minimal Terraform resources per cloud to populate each changed field, then queries them with mql run.
  • Cost and safety guardrails: gates the run when projected spend exceeds $2/hour, requires explicit approval, retries transient apply failures, and always tears down.
  • Bug triage with actionable outputs: reports verification results, separates environment limitations from provider bugs, and creates one combined fix PR for verifiable provider issues.

Quick Start

Trigger this skill for a provider PR (for example, PR #7701) by asking your AI assistant to run provider-verification to provision the smallest Terraform infra needed and verify every changed resource/field against live cloud accounts.

Frequently Asked Questions about provider-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify provider schema changes against live cloud infrastructure?

Verifying provider schema changes against live cloud infrastructure requires provisioning minimal Terraform stacks for altered resources and executing deterministic mql run queries to catch runtime and API-view mismatches that compile-time checks miss.

Why does my provider code compile but fail when querying live cloud APIs?

Provider code compiles but fails when querying live cloud APIs due to runtime and API-view mismatches that compile-time checks miss. Live smoke testing with minimal Terraform provisioning exposes these discrepancies by validating schema fields against real infrastructure.

What is the best way to test mql provider resource diffs in a pull request?

Testing mql provider resource diffs in a pull request is best done via diff-driven verification that extracts changed .lr schemas and .go files, provisions the cheapest Terraform infra, and queries live resources with mql run.

Does provider verification work with Terraform to provision minimal cloud resources?

Provider verification works with Terraform by generating and applying minimal per-cloud Terraform stacks to populate each changed field before running mql queries, ensuring the cheapest-infra smoke testing needed for validation.

How do I triage provider bugs versus environment limitations during cloud integration testing?

Triaging provider bugs versus environment limitations during cloud integration testing involves separating verifiable provider issues from transient apply failures or cloud environment constraints, then creating one combined fix PR for confirmed provider bugs.

What are the cost constraints when provisioning Terraform infra for provider verification?

Cost constraints for provisioning Terraform infra during provider verification include a $2/hour cost gate that pauses runs requiring explicit approval if projected spend exceeds it, while always tearing down provisioned resources afterward.