Skip to content
This repository has been archived by the owner on Nov 20, 2023. It is now read-only.

Dapr extension fails silently if you do not set explicit HTTP bindings #1178

Closed
BigMorty opened this issue Sep 22, 2021 · 0 comments · Fixed by #1194
Closed

Dapr extension fails silently if you do not set explicit HTTP bindings #1178

BigMorty opened this issue Sep 22, 2021 · 0 comments · Fixed by #1194
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@BigMorty
Copy link

Dapr extension fails silently if you do not set explicit HTTP bindings. I did not realize this but if you dont set a binding, it will default to TCP and then Dapr will mysteriously not load side cars or throw errors/warnings (couple of hours debugging this).

Paul did not specify http on the bindings and this made them all start as tcp, which in turn stopped dapr from running the sidecars

Can we do better here, default to http maybe? Detect sidecar not started and give message in log
Maybe a setting to say a sidecar is NOT needed for a service so we can then give a good error message if sidecar does not start

@BigMorty BigMorty added the bug Something isn't working label Sep 22, 2021
@philliphoff philliphoff added enhancement New feature or request and removed bug Something isn't working labels Oct 5, 2021
@philliphoff philliphoff added this to the 0.11 milestone Oct 5, 2021
@philliphoff philliphoff self-assigned this Oct 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants