migrate-to-earl

Migrating raw curl and CLI commands to reusable templates involves scanning source and CI files for provider patterns, importing pre-built templates or creating new ones, validating required secrets, and rewriting call sites with safe staged replacements. This process replaces direct invocations with reviewed template calls to prevent accidental secret leakage and ensure changes are auditable.

The safest way to replace shell script API calls without breaking pipelines is to migrate one provider at a time, run non-destructive test calls where possible, and require a user commit checkpoint before rewriting files. Complex multi-pipe commands should be flagged for manual review rather than being automatically rewritten.

Yes, you can migrate Stripe CLI and GitHub curl calls in Dockerfiles to Earl templates. The process applies grep-based detection across scripts, CI workflows, Dockerfiles, and source files to find provider patterns, then imports or creates the corresponding provider template for each detected command.

Handling secret management when converting HTTP API invocations to templates requires checking and setting template-required secrets during the import or creation flow. The migration process validates these secrets and runs non-destructive test calls before any source files are rewritten to ensure credentials are correctly configured.

Automated CLI migration for complex multi-pipe commands is limited because the tool flags them for manual review rather than attempting automated rewrites. Additionally, staged rewrites are capped at ten call sites per provider to keep changes small and auditable, preventing bulk unreviewed modifications across the codebase.

Your codebase needs staged rewrites when converting raw API calls to templates to make call sites reviewable and reversible. By pausing for a commit checkpoint before rewriting and limiting changes to one provider at a time, the migration reduces the risk of accidental secret leakage and keeps modifications auditable.