dapr-config-validator

DAPR Configuration Validator

This skill automatically validates DAPR configuration files to catch errors before runtime.

When to Use

Claude automatically uses this skill when:

• A YAML file in components/ directory is created or modified
• A dapr.yaml file is created or modified
• User asks to validate DAPR configuration
• Before deployment to catch issues early

Validation Rules

dapr.yaml Validation

# Required structure
version: 1
common:
  resourcesPath: ./components
apps:
  - appId: my-service      # Required: unique identifier
    appDirPath: ./src      # Required: path to app
    appPort: 8000          # Required: application port
    command: ["python", "main.py"]

Checks performed:

• version field present and valid
• apps array is not empty
• Each app has required fields: appId, appDirPath, appPort
• appPort values don't conflict
• Referenced paths exist
• Commands are valid

Component YAML Validation

# Required structure
apiVersion: dapr.io/v1alpha1   # Must be exact
kind: Component                 # Must be exact
metadata:
  name: component-name         # Required: valid name
spec:
  type: state.redis            # Required: valid type
  version: v1                  # Required: valid version
  metadata:                    # Component-specific fields
  - name: redisHost
    value: localhost:6379

Checks performed:

• apiVersion is dapr.io/v1alpha1
• kind is Component
• metadata.name is valid (lowercase, alphanumeric, hyphens)
• spec.type is a valid DAPR component type
• spec.version is specified
• Required metadata fields for component type are present
• No secrets in plain text (warn if found)
• Secret references are properly formatted

Valid Component Types

State Stores:

• state.redis
• state.azure.cosmosdb
• state.postgresql
• state.mongodb
• state.azure.tablestorage

Pub/Sub:

• pubsub.redis
• pubsub.azure.servicebus.topics
• pubsub.kafka
• pubsub.rabbitmq