Aspire project with endpoints but no ports specified won't deploy with "azd up"

[SteveHSX7]

Hi,

I have an Aspire AppHost with a project in it that can have multiple replicas. Each replica can have an http endpoint in it that I can access. When deploying locally for development each replica needs to bind to a separate port as obviously I can't use the same port twice. This configuration in the AppHost :

and in the Silo project :

This enables me to get the dynamic port that the Aspire DCP has supplied so each instance of the project will bind to a different port. This works absolutely perfectly in development locally until I come to deploy to Azure using "azd up" in which case I then get this error :

Which I assume is being caused because I have not specified a port for the endpoint and it doesn't like that.

In the deployment case will I need to specify a port? In this case I can use a specific port as each instance of the project (silo) will be on a different container so port collision is not a concern however I'd like to keep my AppHost as simple as possible and not have too much code that changes between development / deployment (plus I don't really care which port it is on - dynamic is fine).

Or is this a bug or is there some other detail I have missed?

Thanks
Steve H

P.S. As you may have noticed the project is an Orleans Silo that has an Orleans Dashboard in each Silo but that doesn't really matter, it's more the concept I'm asking about.

[davidfowl]

Can you provide a repro project?

[SteveHSX7]

Thanks @davidfowl - I've created a repro project here https://github.com/SteveHSX7/AspireSample with some notes in the README.md that illustrate the problem and some more digging I've done since posting the original problem.