dapr
Remove default scheduler-host-address
Expected Behavior
The scheduler streaming client should not be initialised by default with the run command following changes in 1.14.1. This makes it consistent with the multi-app run for example.
Actual Behavior
A scheduler client connection is initialised and failing to connect.
Steps to Reproduce the Problem
Command:
dapr run --app-id testapp
Result:
Scheduler client initialised with localhost:50006 and failing to connect repeatedly
Release Note
RELEASE NOTE: UPDATE Scheduler client is no longer initialised by default
That is an interesting one because connecting to scheduler by default was done because it is needed for Jobs API to work, even as an alpha feature. Maybe, we change runtime so it does not fail if cannot connect to scheduler? It would also mean that Jobs API is not available to those instances either.
This issue has been automatically marked as stale because it has not had activity in the last 30 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.
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had activity in the last 30 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.
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.