Solution skill
Portman overwriteRequestSecurity drops the API key when key name is omitted
Complete solution
Portman overwriteRequestSecurity drops the API key when key name is omitted. The maintainer identified the bug and fixed it in Portman v1.22.0: upgrade and the API key survives the overwrite even when you only change the value. Use when hitting this exact issue. Not for unrelated errors or different features.
TL;DR
The maintainer identified the bug and fixed it in Portman v1.22.0: upgrade and the API key survives the overwrite even when you only change the value. The docs suggested the key name was optional, but it was required in practice.
Fix
The maintainer identified the bug and fixed it in Portman v1.22.0: upgrade and the API key survives the overwrite even when you only change the value. Expected: You get the expected result; the problem is gone.
When to use
- You are dealing with this situation.
- The symptom matches: Portman overwriteRequestSecurity drops the API key when key name is omitted.
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 v1.22.0).
Variant phrasings
Portman overwriteRequestSecurity drops the API key when key name is omitted
Why it happens
GitHub issue on apideck-libraries/portman: using overwriteRequestSecurity in variation tests to change the apiKey value, but without including the key name, silently removes the API key from the generated Postman collection.
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/portman: using overwriteRequestSecurity in variation tests to change the apiKey value, but without including the key name, silently removes the API key from the generated Postman collection. Resolved: The docs suggested the key name was optional, but it was required in practice. The maintainer identified the bug and fixed it in Portman v1.22.0: upgrade and the API key survives the overwrite even when you only change the value. Source: https://github.com/apideck-libraries/portman/issues/468
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__nt7u7iHUocor2THg2EpJQ" 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">Portman overwriteRequestSecurity drops the API key when key name is omitted <span>— Vectle</span></a>