investigate-deprecated-apis

Scan internal/lightdash/api for deprecated v1 patterns and cross-reference the OpenAPI spec.

16|5|Updated Jul 19, 2023
One-click install
npx skills add https://github.com/ubie-oss/terraform-provider-lightdash --skill investigate-deprecated-apis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigate-deprecated-apis
Source: https://github.com/ubie-oss/terraform-provider-lightdash/tree/main/.claude/skills/investigate-deprecated-apis
Command: npx skills add https://github.com/ubie-oss/terraform-provider-lightdash --skill investigate-deprecated-apis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Accountability for identifying deprecated Lightdash API usage in the provider by comparing code patterns against the official OpenAPI specification. Use when tasked to audit the codebase for technical debt or outdated API dependencies.

Core Features & Use Cases

  • Pattern Discovery: Identify potential uses of deprecated endpoints by scanning internal/lightdash/api for v1 patterns.
  • Spec Cross-Reference: Validate findings against the official OpenAPI spec to confirm deprecation and locate v2 replacements.
  • Impact Analysis: Assess which resources or modules are affected and plan migrations with minimal disruption.

Quick Start

Scan internal/lightdash/api for v1 patterns and cross-check each candidate against the official OpenAPI spec to identify deprecated endpoints and plan migrations.

Frequently Asked Questions about investigate-deprecated-apis

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

FAQPage Schema
How do I find deprecated Lightdash API endpoints in my codebase?

To find deprecated Lightdash API endpoints, scan the internal/lightdash/api directory for v1 patterns and cross-reference each candidate against the official OpenAPI specification to confirm deprecation status. This validates outdated usage and identifies available v2 replacements.

How does OpenAPI spec cross-referencing work for API migration?

OpenAPI spec cross-referencing works by taking candidate endpoints found in code and validating them against the official specification. This confirms whether an endpoint is deprecated and pinpoints the exact v2 replacement endpoint for migration planning.

What is the best way to audit a Terraform provider for outdated API dependencies?

The best way to audit a Terraform provider for outdated API dependencies is to scan code for v1 patterns and cross-reference findings against the official OpenAPI spec. This produces an audit report linking affected Terraform resources to migration steps.

Can I assess which Terraform resources are impacted by deprecated Lightdash APIs?

Yes, you can assess impacted Terraform resources by identifying deprecated Lightdash API usage and summarizing findings in an audit report. This report links affected resources or data sources to recommended migration steps and timelines.

When do I need to scan for v1 API patterns in Lightdash?

You need to scan for v1 API patterns in Lightdash when tasked to audit the codebase for technical debt or outdated API dependencies. This identifies potential deprecated endpoints for migration to v2 replacements using the OpenAPI spec.