eli-173 adding simple container based approach to converting the spec… #32
Conversation
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
…ification to a postman collection
Contributor
|
Might be worth adding something to the README about this? I'm not sure how to run it! (Or am I just missing it?) |
Contributor
|
Running |
…he build context for other machines
…reate-postman-collection-automagically
…reate-postman-collection-automagically
ivma1-nhs
approved these changes
Apr 8, 2025
Contributor
ivma1-nhs
left a comment
ivma1-nhs
left a comment
There was a problem hiding this comment.
Reviewed and tested! Approved
eddalmond1
deleted the
feature/eja-eli-173-create-postman-collection-automagically
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
Experimenting with using existing tooling to generate a postman collection, driven entirely off the specification file. I opted for https://github.com/apideck-libraries/portman/ mainly because it uses openapi-to-postman but was 'friendlier' in terms of actually generating the examples in the specification in the postman collection. There's a lot of extra functionality we might explore as well, if we decide it's a good fit for us (contract tests and nice CI/CD integration, for example).
Context
We ideally would provide a postman collection to our consumers to aid in their development and testing.
Type of changes
Checklist
Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.