anchor.diff:  To set up the caller, supply the calling system with the URL of the generic webhook endpoint for your build:
   
   ****
  -`http://[replaceable]#<openshift_api_host:port>#/osapi/v1beta/buildConfigHooks/[replaceable]#<build-name>#/[replaceable]#<secret>#/generic?namespace=[replaceable]#<namespace>#`
  +`http://_<openshift_api_host:port>_/osapi/v1beta/buildConfigHooks/_<build-name>_/_<secret>_/generic?namespace=_<namespace>_`
   ****
   
   The endpoint can accept an optional payload with the following format:
  
positive.code: command (see link:#describe-buildconfig[below]), and is displayed similar to the following:
  
  ****
  `http://[replaceable]#<openshift_api_host:port>#/osapi/v1beta1/buildConfigHooks/[replaceable]#<build-name>#/[replaceable]#<secret>#/github?namespace=[replaceable]#<namespace>#`
  ****
  
  *Generic Webhooks*
  
negative.code: [#describe-buildconfig]
  *Displaying a BuildConfig's Webhook URLs*
  
  Use the `osc describe buildConfig _<name>_` command to display the Webhook URLs associated with
  a build configuration. If no Webhook URLs are displayed, it means that no Webhook trigger is defined for that
  build configuration.
  
  