Reviewers

r?
cc @stripe/developer-products

Summary

Adds a --dry-run flag to all resource commands (stripe customers create, stripe billing meters list, etc.) and the raw HTTP commands (stripe get, stripe post, stripe delete).

When set, the command prints a JSON preview of the request that would be sent — method, URL, params, and headers — without making any network calls.

Example:

$ stripe customers create --email [email protected] --dry-run
{
  "dry_run": {
    "method": "POST",
    "url": "https://api.stripe.com/v1/customers",
    "params": {
      "email": "[email protected]"
    },
    "headers": {
      "Authorization": "Bearer sk_test_************cdef",
      "Content-Type": "application/x-www-form-urlencoded"
    }
  }
}

Behavior:

• Works without a configured API key — Authorization is omitted from the output rather than failing
• API key is redacted in the output (last 4 chars visible)
• Supports both v1 (form-encoded) and v2 (JSON body) paths, including bracket-notation param nesting (metadata[env]=staging)
• Pagination, expand, idempotency, Stripe-Account, and Stripe-Context params/headers are reflected accurately

Testing:

• Unit tests cover header construction, param parsing (v1 bracket notation, v2 JSON), API-key-absent case, and optional headers
• Parity tests verify that dry-run params match what a live run actually sends for both v1 and v2 paths