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
Aspire: Discover exposed port from the result of dotnet publish
#3073
Comments
Here's the output of the run when
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have the following TODO in the code, which is a corner we cut in our first preview of the aspire work:
azure-dev/cli/azd/pkg/apphost/generate.go
Lines 450 to 462 in 67cfc5a
This should hopefully be straightforward to fix. We need to adjust the
PublishContainer
method on theDotnetCli
type so that we get this information back and the part the JSON object and return it up stack. We also need to update the code in theDeploy
method ofdotnetContainerAppTarget
to then take that result and overwrite the TargetPort value in the context before we evaluate the template.We also need to consider what we do in the
infra synth
case. I suspect we need to publish the container to a local temporary file (which we then delete) so we can get the port that should be exposed from the publish task. Let's chat about what that looks like after we've done the first part. We can always land the first part first and then add theinfra synth
support later.The text was updated successfully, but these errors were encountered: