For Azure API Management, null -> "null"
For a minute, I was pretty happy, having released my first API to Azure API Management. That didn't last, of course, as I learned that it managed to mangle up a simple OpenApi specification.
If you have this in your OpenApi spec:
"schema": {
"type": "string",
"default": null
}
az apim api import bludgeons it to be:
"schema": {
"type": "string",
"default": "null"
}
Which, of course, leads to this in the developer portal:
The fix is simple enough - remove default null from the schema - but what a joke this is. I've heard other tales of APIM modifying, and in the process breaking, you API specifications (which of course is exactly what you're paying for in an API Management tool), but this seemed like such a simple spec that nothing could possibly go wrong. Luckily it did not set "null" as default to int fields...
Thoughts, comments? Send me an email!