microsoft / microsoft/aspire

Set Container Apps Ingress.TargetPortHttpScheme in PublishAsAzureContainerApp

Open
#13,914 0 comments 0 reactions 0 assignees View on GitHub
needs-area-label
Dominant language
C#
Stars
6.3k
Forks
991
Avg merge
2d 15h
Merged PRs (30d)
196

Description

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Is your feature request related to a problem? Please describe the problem.

I'm not sure if this should be here or in the Azure SDK repo, and while technically its still only part of the preview container apps API, I think there are other preview APIs that are available in the ContainerAppsConfiguration using the SDK.

When doing a PublishAsAzureContainerApp, we can specify:
`app.Configuration.Ingress.TargetPort = xxxx;`

but we don't have:
`app.Configuration.Ingress.TargetPortHttpScheme`

Right now I have to aspire deploy, then use az cli to manually change the setting to https. I need https on my container for reasons, and without that the ingress will try http to the container.

Its been in the Container Apps Preview Api since 2023-11-02-preview

### Describe the solution you'd like

It would be great to avoid having to use az cli every deploy and instead be able to just do:

`app.Configuration.Ingress.TargetPortHttpScheme = "https";`

### Additional context

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by tracing PublishAsAzureContainerApp and the app.Configuration.Ingress mapping, then inspect how TargetPort is exposed and serialized for Azure Container Apps. Confirm the preview API's TargetPortHttpScheme shape and verify that configuring "https" is preserved through deployment without requiring a separate az CLI change.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp
Domain
cloud
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.