Repository navigation
feat(postman): import environments, zips and big collections from Postman - #6
Merged
Merged
Conversation
…-all # Conflicts: # apps/web/src/main.js
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Everything the team exports from Postman can be imported, including the large marketplaces collection that failed before.
.zipof a workspace export. Files in the zip that are neither a collection nor an environment are skipped.bun run postman:exportdownloads every collection and environment through the Postman API. The key is read from the environment only.Not covered
Scripts and tests of requests (already out of scope), mocks, flows and monitors. Postman's API does not give globals, so they are exported by hand.
How it was tested
bun run test:ci: 252 tests pass.bun run buildpasses.Refs: TEC-3584