I've been taking a good look at the REST API for Azure DevOps. I'm delighted to say that it's a very full API. However, there's quirks.
I'm writing a tool that interrogates Azure DevOps in order that it can construct release documentation. That release documentation we would like to publish to the project wiki.
To make integration with Azure DevOps even easier, the ADO team have put a good amount of work into client libraries that allow you to code in your language of choice. In my case I'm writing a Node.js tool (using TypeScript) and happily the client lib for Node is written and published with TypeScript too. Tremendous! However, there is a "but" coming....
As I've been using the Node client lib, I've found minor quirks. Such as the
GitApi.getRefs missing the pagination parts of the API.
GitApi was missing some parameters on a method, the
WikiApi was missing whole endpoints, such as the Pages - Create Or Update one. The various client libraries are auto-generated which makes contribution a difficult game. The lovely Matt Cooper has alerted the team
These clients are generated from the server-side controllers, and at a glance, I don't understand why those two parameters weren't included. Full transparency, we don't dedicate a lot of cycles here, but I will get it on the team's radar to investigate/improve.
In the meantime, I still had a tool to write.
Whilst the Node.js client lib was missing some crucial pieces, there did seem to be a way forward. Using the API directly; not using the client lib to do our HTTP and using axios instead. Happily the types we needed were still available for be leveraged.
Looking at the docs it seemed it ought to be simple:
But when I attempted this I found my requests erroring out with 203 Non-Authoritative Informations. It didn't make sense. I couldn't get a single request to be successful, they all failed. It occurred to me that the answer was hiding in
node_modules. I'd managed to make successful requests to the API using the client lib. What was it doing that I wasn't?
The answer ended up being an authorization one-liner:
With this in hand everything started to work and I found myself able to write my own clients to fill in the missing pieces from the client lib:
With this I was able to write code like this:
and the wikis were ours!