sig-api
sig-api copied to clipboard
Repository for Dapr API Special Interest Group
Hello, I have created the following public Postman collection as part of my exploration of Dapr. I would be happy to contribute it to a Dapr repository and maintain it...
It will be great if we forward the `api` subdomain of the Dapr.io website to this repository GitHub Pages: https://dapr.github.io/sig-api/www/ @artursouza @yaron2 any idea who should I reach out to...
Add required headers and metadata schemas supported by the state API to the OpenAPI defintion, following the reference documentation: https://docs.dapr.io/reference/api/state_api/#examples
Adding example bodies to the spec will add examples available to the Swagger UI, but it will also create tests into the generated Postman collection defined in the GitHub actions....
Add example bodies to generate automated tests
Following the reference documentation add missing endpoints for state transactions: https://docs.dapr.io/reference/api/state_api/#state-transactions
@seeflood For practical use, we have added several sets of `saas api` for [layotto](https://github.com/mosn/layotto) and [capa](https://github.com/capa-cloud/cloud-runtimes-jvm) in the past, E.g: + native `s3` api + simple `crypto` api + `email`...
https://github.com/dapr/sig-api/blob/main/README.md The discord channel for `#sig-api` is not accessible - will this be re-created now this is being rebooted?
please visit https://github.com/dapr/dapr/issues/4603
Hi guys, before diving into the details, I think we need to agree on some high-level things, so I wrote this proposal to see your opinions. ## Q: What problems...