4.3 KiB
4.3 KiB
APIM
Z notes on API management so I don’t forget
- API stands for application programming interface. It allows systems to communicate with each other.
- API management (or APIM) is the workstream that aims to provide a new technology platform for Microlise. It introduces a separate layer between customers and Microlise’s existing API products.
The core pillars:
The workflow of publishing API’s:
This is summarised below:
- When someone wants to create an API, they do so by creating a repo and a C# project. Ideally we should use the beautiful templates (https://azdo.microlise.com/MicroliseCollection/Microlise/_git/Microlise.Templates).
- When the engineer wants to deploy this API, it goes through a gated and main pipeline. Phase 2 of the main build will build the image using quay registry so it’s available there (quay.mms.local). The release will consume the artifact produced by the main pipeline and will push these endpoints into the Openshift server. Essentially it will pull the image from the quay registry, containerise it
Then publishing Api's into APIM (API management) using APIOps
- The engineer will need to setup swagger build (docs explains how to do this)
- The engineer will create a PR for an API that has setup the APIOps pipeline (ie added the yaml pipeline and configured the variables - again, docs explain this in detail)
-
There are two pipelines associated with this:
- The gated build: Link (Gated)
- The main build: Link (Main)
- You will see that the term
specis used a lot. This is simply a json/yaml representation of your API interface (what you expose to the customer). - One of the gated tasks is linting, it uses the scripts in this directory to test the OpenAPI specification linting, see: Link.
- Another task adds API Governance Council as reviewers if there are OpenAPI Specification changes. All this can be viewed in the task group (see point a).
- Once the main build passes, it triggers an ApiOps pipeline (defined in step 2), which creates a PR in the APIOps repository (Link)
- Once this PR is reviewed and approved by the Api GC, the Publish pipeline is triggered (Link) which does a 2 way sync so that the APIM environments are in line with the OpenAPI specs. The publisher pipeline runs upto the CERT environment only, the PROD requires approval.
There are two openshift clusters, one is gen and one is prod. Anything not prod goes into gen, and no one can access the prod cluster besides Openshift itself so test well.
The link to the sharepoint site:
Link to the onboarding doc:
The link to the API management API gateway release:
Reverse proxy:
Read up on:
- Quick Start Kubernetes (nigel Poulton)
- How is openshift different from k8? (Link)