Skip to content
← Back to activity

Immutable solution version

Apideck postman-to-k6 mangles auth header keys containing dashes

Version 2Sign in to save

Complete solution

Apideck postman-to-k6 mangles auth header keys containing dashes. The maintainer confirmed the cause and shipped a fix, so upgrading postman-to-k6 to 1.8.5 or later resolves the mangled auth headers. Use when hitting this exact issue. Not for unrelated errors or different features.

TL;DR

The maintainer confirmed the cause and shipped a fix, so upgrading postman-to-k6 to 1.8.5 or later resolves the mangled auth headers. The dash was treated as a special character when chaining properties in the generated k6 code.

Fix

  1. The maintainer confirmed the cause and shipped a fix, so upgrading postman-to-k6 to 1.8.5 or later resolves the mangled auth headers. Expected: You see the expected output instead of the problem.

When to use

  • You are dealing with this situation.
  • The symptom matches: Apideck postman-to-k6 mangles auth header keys containing dashes.

When NOT to use

  • Unrelated issues with a different cause.
  • You need general documentation for the tool; check the official docs instead.

Compatibility

Reported per the linked source (mentions 1.8.5).

Variant phrasings

Apideck postman-to-k6 mangles auth header keys containing dashes

Why it happens

GitHub issue on apideck-libraries/postman-to-k6: converting a Postman collection to k6 mangles authorization keys that contain a dash character, e.g. an x-api-key style header becomes a broken chained expression.

Edge cases

  • If your error message differs even slightly, this is probably a different issue; search the exact text.
  • Behavior can change between releases; the linked source reflects the versions above.
  • If the fix does not help, capture the full error output and check the source link for updates.

Evidence

GitHub issue on apideck-libraries/postman-to-k6: converting a Postman collection to k6 mangles authorization keys that contain a dash character, e.g. an x-api-key style header becomes a broken chained expression. Resolved: The dash was treated as a special character when chaining properties in the generated k6 code. The maintainer confirmed the cause and shipped a fix, so upgrading postman-to-k6 to 1.8.5 or later resolves the mangled auth headers. Source: https://github.com/apideck-libraries/postman-to-k6/issues/62

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_yxOFFml4yVSmZKxT2c5BwA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Apideck postman-to-k6 mangles auth header keys containing dashes <span>— Vectle</span></a>