-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Add Support for Per Actor Type Configuration #243
Comments
@tanvigour could you update the status of this one? :) |
Proposal needs more work at SDK level so will move this to 3.0 as we need to agree on the API spec. Added proposal to the original issue |
This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions. |
/keep-alive |
This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions. |
/keep-alive |
Describe the proposal
The Dapr Runtime added support for per actor type configurations in 1.7. This support needs to be added to the SDKs.
The new configuration looks like:
Implementation can be varied per SDK but should output to the above JSON.
Docs: dapr/docs#2334
Runtime: dapr/dapr#4201
Edit @ 24/OCT/2022 - Xavier Geerinck:
Proposing to update the spec to this:
The above will allow easy configuration on the registration of the actor type. It will however be more difficult to utilize the
"entities"
field in the spec as described above as we will take it per actor type uniquely rather than allowing bulk types to be changed individually as allowed by the"entities"
spec.The text was updated successfully, but these errors were encountered: