Skip to content
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

documentation for the resource group to use for the azurerm_app_service_certificate #23908

Conversation

scott-doyland-burrows
Copy link
Contributor

This updates the documentation for the azurerm_app_service_certificate resource in file website/docs/r/app_service_certificate.html.markdown

The resource_group_name used must be the same as that which the app service plan is defined in.

If the same resource_group_name is not used then terraform will show a successful apply, however the certificate will not be accessible by the app services (and later binding to the certificate will fail).

Also - the certificate will not show in the portal but will show via az webapp config ssl list.

NOTE1 Terraform (or rather the Azure API) behaves differently than the portal. It is possible via the portal to defne/import the certificate into any app service in any resource group and the certificate is then available to all app services - the portal must do some extra "under the covers" work that the API does not.

NOTE2 The various terraform code in the repo has been auto-formatted via terraform fmt hence the large number of formatting changes.

Copy link
Contributor

@manicminer manicminer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@scott-doyland-burrows Thanks for the docs fix and for tidying up the examples. Hopefully this does not cause too may merge conflicts in other open PRs, but this LGTM 👍

@manicminer manicminer merged commit 3275bed into hashicorp:main Nov 20, 2023
@github-actions github-actions bot added this to the v3.82.0 milestone Nov 20, 2023
Copy link

github-actions bot commented May 6, 2024

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants