azure-rest-api-specs
prism
azure-rest-api-specs | prism | |
---|---|---|
7 | 25 | |
2,466 | 4,017 | |
1.7% | 1.5% | |
10.0 | 8.3 | |
3 days ago | 5 days ago | |
TypeScript | TypeScript | |
MIT License | Apache License 2.0 |
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
prism
-
How to Automatically Consume RESTful APIs in Your Frontend
Since the OpenAPI can effectively describe our resources, we can reuse it to generate a dummy server that can be later used for development and testing purposes without bootstrapping any actual services. There some tools available that can help us with this task, such as Prism, OpenAPI Mock, OpenAPI Backend and the MSW library we have already seen.
- The most effective Schema-Driven Development using OpenAPI for Logistic Engineer
-
Show HN: Generate JSON mock data for testing/initial app development
I use https://stoplight.io/open-source/prism with x-faker properties in my OpenAPI specs to mock APIs with dynamic content.
-
Please recommend a good API Mocking tool
Haven't tried it yet, but discovered https://microcks.io/ yesterday. Otherwise https://stoplight.io/open-source/prism is pretty good
-
Prism: a useful developer tool for OpenAPI specs
Prism does more than mocking; You can also use it to inspect any discrepancies between your API implementation and the API spec. You can find out more on their GitHub page:https://github.com/stoplightio/prism
-
How do people deal with mocking CRUD operations for the purposes of testing?
use a mock API server that can read openapi spec (e.g. Prism)
-
Faster time-to-market with API-first
prism
-
install db locally or go with docker image for development?
What about skipping the DB all together and using OpenAPI w/ a Mock Server for local development https://openapi.tools/#mock personally like https://stoplight.io/open-source/prism
- Resurse utile pentru crearea unui REST API?
-
Mock REST APIs with just OpenAPI YAML/JSON
Pretty simple to run [prism](https://github.com/stoplightio/prism) locally for free.