Subsequent deployments reset the Session Affinity flag

[efonsecab]

• Make sure you've installed the latest version using instructions in the wiki

Output from azd version
Run azd version and copy and paste the output here:

Describe the bug
I currently have a platform developed using .NET Aspire. It deploys successfully, however, since I have to manually enable the "Session Affinity" flag after deployment, when I do updates to the code and re-deploy, the "Session Affinity" flag gets reset.

To Reproduce

• Publish a .NET Aspire App using azd deploy
• Enable "Session Affinity" in the deployed container app
• Do a small change to your code.
• Re-Publish the app using azd deploy.

Expected behavior
The Session Affinity flag value persisted in the portal.

Environment
Information on your environment:
* C#, .NET 9
* IDE and version: Visual Studio 17.11.0 Preview 1

Additional context
Add any other context about the problem here.

[rajeshkamal5050]

@vhvb1989 can you triage this?

[vhvb1989]

@efonsecab, this is working as expected per design. When you are working with Aspire, all the infrastructure properties are expected to be set from the appHost. Any manual change is overridden the next time you run a deployment.

However, Aspire does not (yet) support setting up the Azure Container App from the AppHost directly (that's is work in progress).

What you can currently do is to run azd infra synth and apply the session affinity to the yaml file generated by azd which defines the Azure Container App. The downside of this is that after running azd infra synth, you would stop using the AppHost to generate the infrastructure, so if you make changes to your AppHost, you need to run azd infra synth again and re-apply the session affinity changes.

[Steinblock]

@vhvb1989

this is working as expected per design. When you are working with Aspire, all the infrastructure properties are expected to be set from the appHost. Any manual change is overridden the next time you run a deployment.

Except for custom domains which can be prevented from overriding with azd config set alpha.aca.persistDomains on #3955

On the long run an option to set from the appHost might be the best option

var frontend = builder.AddProject<Projects.Frontent>("frontend")
    .WithExternalHttpEndpoints(options => o.SessionAffinity = true)

but currently deploying a blazor app with aspire requires you to setup signalr service which feels a bit of an overkill for smaller apps. So maybe a opt in azd config set alpha.aca.ingressSessionAffinity on might be a good workaround.

[vhvb1989]

I will create azd config set alpha.aca.persistIngressSessionAffinity on to help here