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
feat: add appProtocol and name to var.port_mappings #169
Conversation
2c03cfa
to
18ede8a
Compare
5f2d2d5
to
5e7b037
Compare
variables.tf
Outdated
appProtocol = optional(string) # http, http2, grpc (defaults to tcp) | ||
containerPort = optional(number) | ||
containerPortRange = optional(string) | ||
hostPort = optional(number) | ||
name = optional(string) | ||
protocol = optional(string) # tcp (default), udp |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you please reorder this and keep the same order that we have before and add the new vars after?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure thing 👍
/terratest |
5e7b037
to
fbf9a81
Compare
fbf9a81
to
6c25559
Compare
/terratest |
Just merged earlier PR with the same feature #168 |
the other PR had the additional requirement of setting the err... I see this PR also adds name now. Regardless, I hope that #168 accomplishes what folks needed. I saw some issues regarding ordering of the port mapping config. If that's still an issue we should use this PR to re-order them. |
Hey @max-lobur @dudymas! #168 added Would you like me to refactor this PR to just contain the port range change? We would also want to make |
what
var.port_mappings
(appProtocol
,name
,containerPortRange
)why
references