Skip to content
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

dapr run doesn't allow you to configure placement-port #705

Closed
jkotalik opened this issue May 6, 2021 · 1 comment · Fixed by #746
Closed

dapr run doesn't allow you to configure placement-port #705

jkotalik opened this issue May 6, 2021 · 1 comment · Fixed by #746
Assignees
Labels
good first issue Good for newcomers kind/bug Something isn't working P1
Milestone

Comments

@jkotalik
Copy link

jkotalik commented May 6, 2021

We recently moved from calling daprd to calling dapr run in tye, but it seems like dapr run doesn't allow configuration of the placement port. The property --placement-host-address only allows you to specify the hostname, not port, and always hard codes the dapr port to 6050:

args = append(args, fmt.Sprintf("%s:6050", placementHost))
.

I believe with daprd, we could specify the placement port accordingly in the address: dotnet/tye@3d3164c#diff-8a42fb4a9136d7ed44f58051cf0df30b94f2e6cba21d1c0b2919d56295b6b331. This seems like a regression.

@jkotalik jkotalik added the kind/bug Something isn't working label May 6, 2021
@mukundansundar mukundansundar added this to the v1.3 milestone Jun 3, 2021
@artursouza artursouza added the good first issue Good for newcomers label Jun 22, 2021
@dmitsh
Copy link
Contributor

dmitsh commented Jun 22, 2021

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers kind/bug Something isn't working P1
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants