WIP: Add Backstage Template for Postman Metadata #3
Conversation
This file contains 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
jonico
changed the title
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.
Related to #1
in the Backstage app, highlighting the benefits of using the template for integrating Postman with Backstage.
Dockerfilethat includes a COPY instruction to ensure theapi-creation-postman-template.yamlis part of the Docker image. This change facilitates the deployment of the Postman backstage plugin with the new template included.Introduces a new Backstage template for Postman integration and updates documentation to guide users on its usage.
For more details, open the Copilot Workspace session.
under thetemplates` directory, providing a structured template for creating APIs with Postman metadata in Backstage. This template includes fields for API information and Postman-specific metadata such as