APIOps for Azure API Management: Extracting, Reviewing and Publishing with the CLI

Portal edits to an Azure API Management instance can be silently overwritten when Bicep redeploys the same policy, leaving no record of the change. The article proposes APIOps, which stores APIs, policies and products as files that can be reviewed through pull requests. Ownership is split so Bicep manages the platform while APIOps manages the API surface, controlled by a new apiSurfaceOwner parameter that defaults to bicep. The sample uses the APIOps CLI version 1.0.5, extracting live resources with a filter and running GitHub Actions workflows for nightly extraction and approved publishing. The author notes that nothing was deployed, and that behaviour on a live instance is described only where stated.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in