search

Azure / apiops

APIOps applies the concepts of GitOps and DevOps to API deployment. By using practices from these two methodologies, APIOps can enable everyone involved in the lifecycle of API design, development, and deployment with self-service and automated tools to ensure the quality of the specifications and APIs that they’re building.
https://azure.github.io/apiops
MIT License
328 stars 193 forks source link

[FEATURE REQ] Can we customise the specification file name from the extractor #666

Closed krishnavatsavai closed 1 month ago

krishnavatsavai commented 2 months ago

Please describe the feature.

Currently the extractor is extracting a specification.yaml/json file. It is nice to have the file name configurable. Thank you.

github-actions[bot] commented 2 months ago 
  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.
waelkdouh commented 2 months ago

Why?

guythetechie commented 1 month ago

Sorry, not supported. We rely on the specification file name being consistent for the publisher to work properly.