datadog-pulumi

Resolve Datadog monitor schema and type mismatches in Pulumi YAML.

3|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agent-skills --skill datadog-pulumi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: datadog-pulumi
Source: https://github.com/Cogni-AI-OU/cogni-ai-agent-skills/tree/main/datadog-pulumi
Command: npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agent-skills --skill datadog-pulumi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Datadog monitor definitions often fail when translated from API/JSON or Terraform into Pulumi YAML due to schema differences, type shape mismatches, and provider-specific field mapping.

Core Features & Use Cases

  • Pulumi schema-aligned monitor authoring: Convert Datadog API concepts into the exact Pulumi field names, nesting, and typed shapes required by the Datadog provider.
  • Preview-first troubleshooting: Use pulumi preview validation errors to iteratively rewrite monitors instead of guessing at YAML structure.
  • Mapping and comparator consistency: Ensure threshold math and monitor query comparators match the provider’s expected monitorThresholds behavior to avoid silent logic errors.
  • When to use: Migrating existing monitors into declarative Pulumi YAML, fixing pulumi preview schema/type errors, and safely updating thresholds or query definitions.

Quick Start

Use the datadog-pulumi skill when you hit monitor validation errors during pulumi preview while converting an existing Datadog monitor into Pulumi YAML.

Frequently Asked Questions about datadog-pulumi

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

FAQPage Schema
How do I fix Datadog monitor schema validation errors when migrating to Pulumi YAML?

Fix Datadog monitor schema validation errors by using pulumi preview failures to iteratively rewrite YAML fields, mapping API JSON or Terraform definitions to the exact typed shapes and nesting expected by the Pulumi Datadog provider.

Why does my Datadog monitor threshold logic fail after converting to Pulumi YAML?

Datadog monitor threshold logic fails due to type shape mismatches between API definitions and Pulumi provider schemas, requiring threshold math and query comparators to be mapped to the correct monitorThresholds behavior to prevent silent logic errors.

Can I convert Datadog Terraform monitors directly into Pulumi YAML?

You can convert Datadog Terraform monitors into Pulumi YAML by resolving field mapping differences and applying schema discovery via pulumi package get-schema to align the definitions with provider-specific types before validation.

What is the best way to troubleshoot pulumi preview failures for Datadog monitors?

The best way to troubleshoot pulumi preview failures for Datadog monitors is preview-first iterative repair, using the validation errors to drive repeated YAML rewrites until the schema and type alignment succeeds.

Does converting Datadog API JSON to Pulumi YAML require provider schema discovery?

Converting Datadog API JSON to Pulumi YAML requires provider-schema discovery via pulumi package get-schema to identify correct Pulumi field names, nesting structures, and typed shapes for successful monitor validation.

When should I not use Pulumi YAML for Datadog monitor management?

You should not use Pulumi YAML for Datadog monitor management if your infrastructure stack does not support Pulumi or if you need to avoid iterative preview-driven rewrites required to resolve type shape mismatches and schema differences.