You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: