dapr / dapr/docs

Add documentation detailing all possible ingress routes on app

Open
#4,474 1 comment 1 reaction 0 assignees View on GitHub
content/missing-information
Dominant language
SCSS
Stars
1k
Forks
794
Avg merge
2d 8h
Merged PRs (30d)
7

Description

**What content needs to be created or modified?**
There are a great many routes that are automatically created by the various SDKs into an application. It'd be nice to get a document that details each of them so that network operators can more easily set up blacklists on load balancing filters so external traffic doesn't readily hit Dapr-created endpoints.

**Describe the solution you'd like**
Create documentation with a list of each of the route patterns for each building block.

**Where should the new material be placed?**
I wouldn't think that most of this is SDK specific, but it might bear some research on that front. If it's not SDK-specific, probably somewhere under https://docs.dapr.io/reference/ would be a good place. Otherwise, if _any_ of the routes depend on the SDK, common endpoints should be located in the reference doc with references to the SDK-specific routes to their own respective documentation endpoints.

**The associated pull request from dapr/dapr, dapr/components-contrib, or other Dapr code repos**
New content request - haven't written/researched it yet

**Additional context**
Happy to take this on myself, but don't know if I can commit to a 1.15 release or not. It could be released anytime after 1.15 as I'll include those routes as well.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.