[Question] What is recommended practices for developers when making changes to our api specification
- Dominant language
- C#
- Stars
- 448
- Forks
- 247
- PR merge metrics
- No merged PRs in 30d
Description
### Release version
Not sure
### Question Details
Creating a new API in APIM from an API spec (using swagger) is super easy with some caveats.
Go into API, upload openAPI spec, run extract pipeline, the artifacts here and there, and then commit and publish.
Where i'm struggling is making modifications. There are so many things that differ when running in APIM vs what is extracted from a swagger API spec makes this very difficult. For example, all my serviceUrls, OAuth security protocols, examples, etc get wiped or modified even adding a single property to an API is annoying.
We basically have to manually do everything, or optionally completely republish/extract but that removes API from developer portal during the process.
### Expected behavior
Maybe break up api specification up in a way that might be easier to digest and only need to modify particular files. Maybe provide a openapi specification (extracted from service) and have overrides in other configuration files for securityschemas as an example.
### Actual behavior
everything is contained in api specification
### Reproduction Steps
I think i put enough detail above.
Contributor guide
Assessment
This issue has not been assessed yet.