documentation for the resource group to use for the azurerm_app_service_certificate #23908
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This updates the documentation for the
azurerm_app_service_certificate
resource in filewebsite/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.