You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repository seems dead, and the code contains issues like hard coded path value (this is the suffix for your API endpoint) on the update request. I took and forked it, made some additions like support for local definition file (as this one only supports a publicly hosted file), as well as some more checks and of course unit tests. I also extended the documentation quite a bit, explaining what some values are, how they are build, where you can find them etc.
Already put it to use on my own project and it's working fine. Motivation for this was that I had an OpenAPI schema definition file on my Azure Functions project and I needed to keep my API in front of it updated, but without manual work. There is still some manual work, like mapping a new endpoint to a functions app, but that's the only thing I haven't figured out yet.
You can drop comments and also join to collaborate if you'd like. I am a full time developer who also does a lot of freelancing where I rely on open source projects, so I will try to maintain this if needed.
The only downside is (and this is beyond my control) that Azure API Management API doesn't support YAML files. I have to either convert my definitions to JSON or maybe run some YAML to JSON conversions automatically when committing to automate that too (my own problem :)
The text was updated successfully, but these errors were encountered:
This repository seems dead, and the code contains issues like hard coded path value (this is the suffix for your API endpoint) on the update request. I took and forked it, made some additions like support for local definition file (as this one only supports a publicly hosted file), as well as some more checks and of course unit tests. I also extended the documentation quite a bit, explaining what some values are, how they are build, where you can find them etc.
Already put it to use on my own project and it's working fine. Motivation for this was that I had an OpenAPI schema definition file on my Azure Functions project and I needed to keep my API in front of it updated, but without manual work. There is still some manual work, like mapping a new endpoint to a functions app, but that's the only thing I haven't figured out yet.
You can drop comments and also join to collaborate if you'd like. I am a full time developer who also does a lot of freelancing where I rely on open source projects, so I will try to maintain this if needed.
https://github.com/OssiPesonen/action-update-api-management-openapi
The only downside is (and this is beyond my control) that Azure API Management API doesn't support YAML files. I have to either convert my definitions to JSON or maybe run some YAML to JSON conversions automatically when committing to automate that too (my own problem :)
The text was updated successfully, but these errors were encountered: