- timothymaguireSmartBear Alumni (Retired)Status changed:Selected for DevelopmenttoImplemented
- timothymaguireSmartBear Alumni (Retired)
This has been implemented for Source Control integrations (GitHub, BitBucket, Azure DevOps, GitLab)
- timothymaguireSmartBear Alumni (Retired)Status changed:New IdeatoSelected for Development
- deltafsdevNew Contributor
I also would find this feature useful - particularily the templating - as I want to do this: sync each API with a folder in the same repo in Git Azure DevOps with the path /APIs/<<API_NAME>>/<<Version>>, presently I will need to configure each one of these separately. Thanks.
- TanyaYatskovskaSmartBear Alumni (Retired)Status added:New Idea
- jubrNew Member
Yes, please add this feature. We're planning to use the SwaggerHub to keep track of all of our internal APIs, probably close to 50. Imagine having to fill out all the integration plugin forms by hand for multiple integrations per api per version.
Maybe then also introduce some kind of variable substitution in the plugin configurations. The `branch` name for the SCM plugins could then be configured as `swaggerhub-${apiVersion}` for instance?
As an intermediate option perhaps it could be an idea to offer the user the option to copy integrations from another version?
Related Content
- 14 years ago
- 5 years ago
- 10 years ago