Our great sponsors
-
-
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.
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
Agree here. When I was on the API Management team, I generally saw customers set up a repository of API specifications (incidentally, this is also how we do it internally at Microsoft - check it out at https://github.com/azure/azure-rest-api-specs) - those specifications generally drive the API Management side of things, but with review from a centralized API management team. The “spec” should consist of both the specification (Swagger, SOAP, GraphQL SDL, etc.) and the policy or policies appropriate for the API.
The Azure APIOps Toolkit (here: https://github.com/Azure/APIOps) provides a toolkit on top of git to version control your APIs and ensure that updates to the API Management service can be change controlled, approved, and minimally invasive to other running APIs. It takes a little bit to set it up, but I highly recommend it.
Related posts
- Are subscriptions idempotent when deployed via Bicep? I seem to have some issue with them after having success the first time.
- How to manage APIM as Infrastructure as Code (IaC)?
- StackQL provider for Azure is now available
- Azure Bicep - How do I know what property values are valid?
- apiVersion deprecation