DBOMproject / DBOMproject/docs
Support Postman Environments
- Dominant language
- Python
- Stars
- 2
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
**System information**
- Version of Services: 2.0.0-aplha
- Are you willing to contribute it (Yes/No): Yes
**Describe the feature and the current behavior/state.**
Currently the postman collection uses collection variables, but that means that if you want to interact with a different node, you need to change the referenced variables in every request you want to use. With an env, you could have an env for each node, so you just switch env when you want to interact with the other node, and all the requests will fall in line
**Will this change the current API? How?**
No
**Who will benefit with this feature?**
Make the postman collection easier to use
**Miscellaneous Information**
Contributor guide
Research direction
No source file or test is named in the issue. Start by locating the Postman collection and its current collection-variable definitions, then check how requests reference the node values. Done means users can select an environment for each node without editing variables in individual requests, while the API remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postman
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100