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

Support for Health Check evaluation period in Azure Functions #10282

Closed
maximivanov opened this issue Jan 22, 2021 · 2 comments
Closed

Support for Health Check evaluation period in Azure Functions #10282

maximivanov opened this issue Jan 22, 2021 · 2 comments

Comments

@maximivanov
Copy link

Community Note

  • 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

Description

We can configure the health check path on a Function App with Terraform.
Azure Portal also allows configuring the time that an unhealthy instance remains in the load balancer before it is removed:

Screen Shot 2021-01-22 at 12 59 08

It would be nice to have support for that in Terraform too.

New or Affected Resource(s)

  • azurerm_function_app

Potential Terraform Configuration

resource "azurerm_function_app" "function_app" {
  ...
  health_check_evaluation_period = 5
}

References

@maximivanov
Copy link
Author

I realized the health check evaluation period is configured with an application setting, not on the function app resource itself.

resource "azurerm_function_app" "function_app" {
  ...
  app_settings = {
    ...,
    "WEBSITE_HEALTHCHECK_MAXPINGFAILURES" = "5"
  }
}

Closing as irrelevant.

@ghost
Copy link

ghost commented Feb 22, 2021

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Feb 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant