Add Platform Support

None - the skill handles everything automatically.

Usage

Interactive Mode (Recommended)

/add-platform-support

The skill will prompt you for:

• Platform ID (e.g., "hetzner")
• Platform name (e.g., "Hetzner Cloud")
• Metadata URL (e.g., "http://169.254.169.254/hetzner/v1/userdata")
• Documentation URL (e.g., "https://www.hetzner.com/cloud")
• Optional: Custom description

Direct Mode

/add-platform-support --id hetzner --name "Hetzner Cloud" --url "http://169.254.169.254/hetzner/v1/userdata" --docs "https://www.hetzner.com/cloud"

Step-by-Step Workflow

When invoked, follow these steps in order:

Step 1: Gather Required Information

If not provided as arguments, ask the user for:

Required:

• provider_id: Platform ID (lowercase, alphanumeric, e.g., "hetzner")
• provider_name: Display name (e.g., "Hetzner Cloud")
• metadata_url: Full URL to fetch config from
• provider_url: Documentation URL for the platform

Optional:

• description: Custom description (default: "Ignition will read its configuration from the instance userdata. Cloud SSH keys are handled separately.")

Validation:

• Provider ID must be lowercase, alphanumeric (no spaces, no special chars except hyphen)
• Provider ID must not already exist in internal/providers/
• URLs must be well-formed

Step 2: Determine Current Spec Version

Find the latest experimental spec version:

# List config spec directories
ls -d internal/config/v*_experimental/ | sort -V | tail -1

Extract the version (e.g., v3_6_experimental) to use in import paths.

Step 3: Parse Metadata URL

Parse the metadata URL to extract components: