anchor.diff:  ----
   http://<openshift_api_host:port>/oapi/v1/namespaces/<namespace>/buildconfigs/<name>/webhooks/<secret>/generic
   ----
  +
  +The caller must invoke the webhook as a `*POST*` operation.
  +
  +To invoke the webhook manually you can use `*curl*`:
  +
  +----
  +$ curl -X POST -k https://<openshift_api_host:port>/oapi/v1/namespaces/<namespace>/buildconfigs/<name>/webhooks/<secret>/generic
  +----
  +
  +The HTTP verb must be set to `*POST*`. The insecure `*-k*` flag is specified to ignore certificate validation. This second flag is not necessary if your cluster has properly signed certificates.
   
   The endpoint can accept an optional payload with the following format:
   
  
positive.code: trigger on your `*BuildConfig*` and trigger it via your Gogs server also.
  ====
  
  
  *Generic Webhooks*
  
  
negative.code: this behavior.
  ====
  
  To pass this payload using `curl`, define it in a file named *_payload_file.yaml_* and run:
  
  ----
  $ curl -H "Content-Type: application/yaml" --data-binary @payload_file.yaml -X POST -k https://<openshift_api_host:port>/oapi/v1/namespaces/<namespace>/buildconfigs/<name>/webhooks/<secret>/generic
  ----
  
  The arguments are the same as the previous example with the addition of a header and a payload. The `*-H*` argument sets the `*Content-Type*` header to `*application/yaml*` or `*application/json*` depending on your payload format. The `*--data-binary*` argument is used to send a binary payload with newlines intact with the `*POST*` request.
  
  [[describe-buildconfig]]
  
  *Displaying a BuildConfig's Webhook URLs*
  