azurerm_container_app - Support for managed TLS certificate
### Is there an existing issue for this? - [X] I have searched the existing issues ### Community Note <!--- Please keep this note for the community ---> * Please vote on this issue by adding a :thumbsup: [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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 <!--- Thank you for keeping this note for the community ---> ### Description Container Apps has a public preview of managed SSL certs available (see microsoft/azure-container-apps#607). The `azurerm_container_app` resource is already kind of tough to use with external domains, requiring either complex logic on when to include a custom domain block and multiple terraform runs, or manually commenting out the custom domain block until your validation records exist. The validation records are almost exactly the same as in Azure App Service, so this would be much easier if we could follow the app service pattern via new resources - `azurerm_container_app_custom_hostname_binding` and `azurerm_container_app_certificate_binding`. Based on the cli in microsoft/azure-container-apps#607, I don't think it needs a separate `azurerm_container_app_managed_certificate`
Posted by jtatum on May 21, 2023, 4:28 PM
Tags
Related issues
- I hate that this whole cluster of beliefs exists, but software on my own computer enforcing what I can and can't do for ideological reaso...
- As I replied in another comment[1], it's their software, their choice.
- [Feature] Support external model integration via personal API keys and local LLMs (BYOK)
- > So when head of companies don’t care about quality, they’ll push hard no matter what to have speed.
- Feature request: support multiple named accounts per app/connector
- Support standalone Windows installer (`codex-setup.exe`)
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
support (SaaS)
I hate that this whole cluster of beliefs exists, but software on my own computer enforcing what I can and can't do for ideological reaso...
NewAs I replied in another comment[1], it's their software, their choice.
[Feature] Support external model integration via personal API keys and local LLMs (BYOK)
> So when head of companies don’t care about quality, they’ll push hard no matter what to have speed.
Feature request: support multiple named accounts per app/connector
Support standalone Windows installer (`codex-setup.exe`)
[feature]: Move OIDC back to self-hosted OSS(Plane Free)
I was running about 1000 machines on VMware in my previous career.
azurerm_container_app - Support for managed TLS certificate
### Is there an existing issue for this? - [X] I have searched the existing issues ### Community Note <!--- Please keep this note for the community ---> * Please vote on this issue by adding a :thumbsup: [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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 <!--- Thank you for keeping this note for the community ---> ### Description Container Apps has a public preview of managed SSL certs available (see microsoft/azure-container-apps#607). The `azurerm_container_app` resource is already kind of tough to use with external domains, requiring either complex logic on when to include a custom domain block and multiple terraform runs, or manually commenting out the custom domain block until your validation records exist. The validation records are almost exactly the same as in Azure App Service, so this would be much easier if we could follow the app service pattern via new resources - `azurerm_container_app_custom_hostname_binding` and `azurerm_container_app_certificate_binding`. Based on the cli in microsoft/azure-container-apps#607, I don't think it needs a separate `azurerm_container_app_managed_certificate`
Comments (0)
No comments yet. Start the discussion.