Support basic Admin API

[tjoubert]

GET/_admin/log/entries Read global logs from the server
POST/_admin/routing/reload Reloads the routing information
GET/_admin/server/id Return id of a server in a cluster
GET/_admin/server/role Return role of a server in a cluster
GET/_api/engine Return server database engine type
GET/_api/version Return server version

[DiscoPYF]

Thanks @tjoubert 🥳 I left a bunch of comments but only one of them is a blocker in GetLogsQuery.

I noticed a couple of endpoints from the online doc that have not been added here. Is that on purpose? e.g. GET /_admin/server/availability

[DiscoPYF]

Should the changelog file be updated?

[tjoubert]

[tjoubert]

Should the changelog file be updated?

I will prefer to update the changelog and the roadmap files immediately after the merge so as to avoid conflicts when we have multiple PRs open.

[tjoubert]

Thanks @tjoubert 🥳 I left a bunch of comments but only one of them is a blocker in GetLogsQuery.

I noticed a couple of endpoints from the online doc that have not been added here. Is that on purpose? e.g. GET /_admin/server/availability

Thanks @DiscoPYF. Yes, there are a lot more Admin API endpoints. We're implementing a small subset for now to support features that we will implement very soon.

[DiscoPYF]

We're implementing a small subset for now to support features that we will implement very soon.

Could you elaborate a bit on that? Features for this C# library or ArangoDB? Maybe creating issues where we paste a bit more context would help answer those questions beforehand.
I see that all branches are created after a specific number. I suppose you have an issue tracker internally in the ArangoDB org?

[tjoubert]

@DiscoPYF, yes we use another tool internally to track projects and issues. These endpoints had to be implemented to bring the C# driver up to date with our other drivers like Java and JS. In terms of future development, we have some ideas of tools that will be useful to the C# community but no firm development plan for these yet. For now, we're focused on supporting features from the ArangoDB API.