anchor.diff:  ###health-check
   File location: `<plan>/hooks/health-check`
   
  -This hook is run when the Chef Habitat HTTP API receives a request at `/health`.
  +This hook is run periodically on a configurable interval.
   
   The `health-check` script must return a valid exit code from the list below.
   
  
positive.code: 
  An `install` hook, unlike other hooks, will not have access to any census data exposed via binds or the `svc` namespace. Also, configuration in `svc_config_path` is not accesible to an `install` hook. If an `install` hook needs to utilize templated configuration files, templates located in the `svc_config_install_path` may be referenced. This location will contain rendered templates in a package's `config_install` folder. Finally, any configuration updates made during a service's runtime that would alter an `install` hook or any configuration template in `svc_config_install_path` will not cause a service to reload.
  
  ###reload
  File location: `<plan>/hooks/reload`
  
  For processes that can update their configuration without requiring a restart a `reload` hook can be written. This hook will execute instead of the default behaviour of restarting the process. `{{pkg.svc_pid_file}}` can be used to get a handle on the `PID` of the service.
  
  ###reconfigure
  File location: `<plan>/hooks/reconfigure`
  
  This hook is run when service configuration has changed due to updates coming from the gossip protocol or from the `user.toml` file. Before the `reconfigure` hook the config files are re-rendered and the process is either restarted or the `reload` hook is called if present.
  
  ###suitability
  File location: `<plan>/hooks/suitability`
  
negative.code: Each plan can specify lifecycle event handlers, or hooks, to perform certain actions during a service's runtime. Each hook is a script with a [shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)) defined at the top to specify the interpreter to be used. On Windows, Powershell Core is the only interpreter ever used.
  
  To define a hook, simply create a bash file of the same name in `/my_plan_name/hooks/`, for example, `/postgresql/hooks/health-check`.
  
  When applying a new configuration, modification to the `run` or `post-run` hooks will restart the service.
  
  > **Important** You cannot block the thread in a hook unless it is in the `run` hook. Never call `hab` or `sleep` in a hook that is not the `run` hook.
  
  