azure-rest-api-specs
autorest
azure-rest-api-specs | autorest | |
---|---|---|
7 | 12 | |
2,466 | 4,486 | |
1.7% | 0.3% | |
10.0 | 7.7 | |
3 days ago | 8 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
azure-rest-api-specs
-
Shared APIM Service
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.
- Are subscriptions idempotent when deployed via Bicep? I seem to have some issue with them after having success the first time.
-
StackQL provider for Azure is now available
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.
-
LocalStack 1.0 General Availability
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...
-
Implementing Microsoft REST API Guidelines Filter
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
-
Azure Bicep - How do I know what property values are valid?
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
-
apiVersion deprecation
You might get some clues here. Maybe. https://github.com/Azure/azure-rest-api-specs
autorest
-
How to auto generate automation code for existing apis?
Doesn't autorest do that? https://github.com/Azure/autorest
-
MDN = Markdown
The autorest project uses this actually.
It works by embedding yaml code blocks into a markdown file.
It’s actually not completely awful and has proven somewhat useful to have a configuration clearly documented within the config.
https://github.com/Azure/autorest/blob/main/docs/generate/re...
-
StackQL provider for Azure is now available
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.
-
The Collison Brothers Built Stripe into a $95B Unicorn
I wonder if there is a format for API -> client automation that can be good enough, in the end Stripe have a rest API, with enough description it should be possible.
Okay so after a quick google it appears Microsoft are the "Simpsons already done it" of the programming world: https://github.com/Azure/autorest/
It'd probably be a good idea to add an Elixir backend for that and point it at Stripe's API here: https://github.com/stripe/openapi
-
i learned the basics of how to create and use the MS Graph API. here's my notes
It is definitely created with AutoRest. That's both its strength and its greatest weakness. :(
-
Creating and Using HTTP Client SDKs in .NET 6
Honorable mentions: AutoRest, Visual Studio Connected Services
-
New Microsoft Graph PoSH module
The Microsoft.Graph.* modules are AutoRest-generated modules. They are a straight wrapper around the REST calls that you would perform with Invoke-RestMethod or Invoke-WebRequest.
- Adopting the OpenAPI schema to generate Plaid’s SDKs
- Which is the best code generator for consuming RESTful API that uses Swagger?
-
Any way to generate Typescript code from API in Mac/OSX or Linux like NSwag Studio?
You can try autorest. I haven't used NSwag but I believe the two are similar. Also it looks like Nswag has a command line tool that you could use.
What are some alternatives?
prism - Turn any OpenAPI2/3 and Postman Collection file into an API server with mocking, transformations and validations.
NSwag - The Swagger/OpenAPI toolchain for .NET, ASP.NET Core and TypeScript.