azure-rest-api-specs VS stackql-provider-registry

Agree here. When I was on the API Management team, I generally saw customers set up a repository of API specifications (incidentally, this is also how we do it internally at Microsoft - check it out at https://github.com/azure/azure-rest-api-specs) - those specifications generally drive the API Management side of things, but with review from a centralized API management team. The “spec” should consist of both the specification (Swagger, SOAP, GraphQL SDL, etc.) and the policy or policies appropriate for the API.

The StackQL Azure provider was created using the Autorest project using Azure specification docs from the azure-rest-api-specs repository. We will be adding integrated interactive authentication; for now, this is cli/sdk based; you can find all the documentation here.

In the spirit of moto, it actually looks like quite a bit of the groundwork is available for someone to take a swing at an Azure version:

* the cli uses the python SDK: https://github.com/Azure/azure-cli/blob/azure-cli-2.38.0/src...

* which uses autorest: https://github.com/Azure/azure-sdk-for-python/tree/azure-mgm...

* of what appears to be an OpenAPI-ish spec: https://github.com/Azure/azure-rest-api-specs/tree/fda2db441...

I'm not sure what you mean by "it is very hard to give contextuality on it"; OAS does supports referring to a type by reference, so that higher level types can reuse the definition of structs they might contain.

But even so, here the problem is that the APIs aren't actual PUT/GETs: they payload types aren't the same going up as they are coming down. It is really two separate types, one for PUT, one for GET.

Some of that is to be expected (there will be some information after the create that is only added by the VM coming into being) but how Kubernetes handles this with a separate "status" for the item I think ends up letting the rest of the type (spec, in k8s's case) be the same type. (… ish. K8s has variants of this problem, too.)

To expand a bit, I'm largely relegated to the API docs themselves. Browsing the actual schema is hard:

  Start at: https://github.com/Azure/azure-rest-api-specs

I feel your pain, a good resource for me has been the REST API specs - https://github.com/Azure/azure-rest-api-specs/tree/master/specification

You might get some clues here. Maybe. https://github.com/Azure/azure-rest-api-specs

Hi HN, we have an open-source project called StackQL which can be used for CSPM, cross-provider UAM/entitlements reporting, inventory analysis, and finops across different public cloud and SaaS providers; see https://github.com/stackql/stackql-provider-registry. In addition, StackQL can be used for IaC (across different cloud providers), including multi-cloud transaction and rollback capability, which we are building out. Can be used standalone (in exec or server mode running a postgres wire protocol server) or using Docker, Python, Jupyter, within GitHub Actions (incl https://github.com/marketplace/actions/stackql-studios-stack... and https://github.com/marketplace/actions/stackql-studios-stack...) and more.

The project can also be used with a private registry (API provider) as an application query interface - like GraphQL - except using SQL statements and transformations (including scalar and aggregate functions, joins, unions, and table-valued functions - see https://github.com/stackql/stackql-middleware and https://github.com/stackql/stackql-playground.

We are looking for contributors!! The core project is written in Golang with tests implemented using the Robot framework and Python. We have about 40 related repos in our org, spanning Python, Jupyter, JavaScript/TypeScript (Deno and NodeJS). Let us know what you think!

We are looking for Azure enthusiasts to road-test it! Reach out here if you are interested.