anchor.diff:  * If your `BuildConfig` has a `Git` source type defined, it is dynamically
   disabled, since `Binary` and `Git` are mutually exclusive, and the data in
   the binary stream provided to the builder takes precedence.
  +
  +Instead of a file name, you can pass a URL with HTTP or HTTPS schema to
  +`--from-file` and `--from-archive`. When using  `--from-file` with a URL, the
  +name of the file in the builder image is determined by the `Content-Disposition`
  +header sent by the web server, or the last component of the URL path if the
  +header is not present. No form of authentication is supported and it is not
  +possible to use custom TLS certificate or disable certificate validation.
   
   When using `oc new-build --binary=true`, the command ensures that the
   restrictions associated with binary builds are enforced. The resulting
  
positive.code: to `false` (the default setting) in the master configuration file, linking
  secrets to a service is not required.
  ====
  
  [[manual-addition-of-a-source-secret-to-a-build-configuration]]
  ==== Manually Adding Source Clone Secrets
  
negative.code: stream to the builder. The builder then extracts the contents of the archive
  within the build context directory.
  
  * `--from-archive`: The archive you specify is sent to the builder, where it is
  extracted within the build context directory. This option
  behaves the same as `--from-dir`; an archive is created on your host first,
  whenever the argument to these options is a directory.
  
  In each of the above cases:
  
  * If your `BuildConfig` already has a `Binary` source type defined, it will
  