I have been using Postman GUI for macOS for a while and have an “environment” file with a disabled key:
{
"id": "…",
"name": "…",
"values": [
…,
{
"key": "foo",
"value": "38",
"enabled": false
}
],
"_postman_variable_scope": "environment",
"_postman_exported_at": "2023-04-03T21:43:51.080Z",
"_postman_exported_using": "Postman/10.12.9"
}
When I run via the Postman GUI, it honors this enabled of false. But when I run from Postman CLI (version 1.1.1 on macOS w Apple silicon), it does not honor this setting.
My kludgy fix is to just change the name of this key to something else that won’t be picked up by my tests, but it just seems wrong to have to do this. The Postman CLI should honor the enabled setting of false.
FYI.
Posted as comment on existing to GitHub issue:
opened 01:49PM - 20 Dec 22 UTC
bug
product/runtime
postman-cli
### Is there an existing issue for this?
- [X] I have searched the tracker for … existing similar issues and I know that duplicates will be closed
### Describe the Issue
I have 2 variables in my enviroment variable list.
Those 2 have the same name, but the last one is disabled. In (regular) postman it is grayed out.
When I run the collection using postman-cli, this disabled variable is not ignored, but it is used.
So it overwrites the enabled variable.
### Steps To Reproduce
1. use your favorite collection.
(make sure it runs without problems)
2. copy a variable in the enviroment variable list.
(for example: _hostname_)
3. change the value of the 2nd variable (for example: disabled.postman.com)
4. disable the 2nd entry (but do not delete it)
(in postman it is grayed out)
5. run the collection in postman. This should still pass.
6. run the collection again, now using postman-cli
result: the postman-cli uses the value of the disabled 2nd variable (containing 'disabled.test.com') instead of the expected value of the first variable.
### Screenshots or Videos
_No response_
### Operating System
Windows and Linux
### Postman Version
postman 10.6.7 + postman-cli 1.0.8
### Postman Platform
Postman App
### User Account Type
Signed In User
### Additional Context?
_No response_