You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.
Description
Currently the exposed port on azurerm_container_app is missing. It is needed when you want to expose a different port than the target port. It is available if the transport is TCP. It is already supported but not documented (would be nice to document it). It was made possible when the API version was updated in #22804.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Is there an existing issue for this?
Community Note
Description
Currently the exposed port on azurerm_container_app is missing. It is needed when you want to expose a different port than the target port. It is available if the transport is TCP. It is already supported but not documented (would be nice to document it). It was made possible when the API version was updated in #22804.
The latest version of the SDK is being used and the field is available already https://github.com/hashicorp/go-azure-sdk/blob/2f16ee0d84fbe0ebc235a86357d6b421190f6736/resource-manager/containerapps/2023-05-01/containerapps/model_ingress.go
New or Affected Resource(s)/Data Source(s)
azurerm_container_app
Potential Terraform Configuration
References
No response
The text was updated successfully, but these errors were encountered: