Open jolo-dev opened 11 months ago
Thanks @jolo-dev for the inputs and pull request.
Wouldn't this occur in a breaking change
as we will have a parameter type changed?
Could we instead add another property as @jolo-dev mentioned, containerPorts: PortMapping[]
, and evaluating which will be passed to Cfn on building time? (both fields provided = error)
Another alternative would be marking the current containerPort
as Deprecated and create the new field as mentioned.
WDYT?
Hey @paulosergio-jnr,
Yeah you're right. It would be a breaking change. I think making it Deprecated
and creating a new field would be the cleaner approach.
Describe the feature
When using for example
ApplicationLoadBalancedFargateService
you can pass intaskImageOptions
. However, thecontainerPort
is from typenumber
but should be aPortMapping[]
instead. I ran into the issue that I needed that because my container exposed multiple Ports thus I had to create ataskDefinition
due to that.Use Case
Container, which exposes multiple ports. This is possible through
taskDefinition
but would bloat the codebase.Proposed Solution
Instead of
containerPort: number
, it should becontainerPorts: PortMapping[]
.Other Information
No response
Acknowledgements
CDK version used
2.110.0
Environment details (OS name and version, etc.)
MacOS 14.1