Container property should both describe and set port

[willtsai]

Overview of feature request

Currently, the Applications.Core/containers.properties.container.ports property is being used to describe or document the port that is exposed by the container to serve incoming traffic. This has potential to be confusing for users who might expect that this property actually sets the port (and not just describe/document) that is exposed or forwarded by the container.

Thus, the proposal here is to change the behavior of the Applications.Core/containers.properties.ports property to explicitly override or set the port that is exposed by the container, in addition to documenting the port.

Acceptance criteria

When the user specifies the Applications.Core/containers.properties.container.ports, an override is created for the container to expose the user specified port instead of the port originally offered by the container.

Additional context

This request originated from PR radius-project/samples#748 to address radius-project/docs#916, where there was some confusion regarding which port the container ends up offering when the Applications.Core/containers.properties.container.ports differs from the originally offered port in the container.

Will need to explore how to accomplish the override, which might differ by app framework, e.g. for .NET apps, the port override can be provided as an env variable - https://learn.microsoft.com/en-us/aspnet/core/fundamentals/host/web-host?view=aspnetcore-3.1#server-urls-2

AB#10034

[radius-triage-bot]

👋 @willtsai Thanks for filing this feature request.

A project maintainer will review this feature request and get back to you soon.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

[radius-triage-bot]

👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview