anchor.diff:    dockerfile: "FROM centos:7\nRUN yum install -y httpd" <4>
   ----
   <1> The `*binary*` field specifies the details of the binary source.
  -<2> The `*asFile*` field specifies the name of a file that will be created with
  +<2> The `*asFile*` field specifies the name of the file that will be created with
   the binary contents.
  -<3> The `*contextDir*` field specifies a subdirectory with the contents of a
  +<3> The `*contextDir*` field specifies a subdirectory within the extracted contents of a
   binary archive.
   <4> If the optional `*dockerfile*` field is provided, it should be a string
   containing an inline Dockerfile that potentially replaces one within the
  
positive.code: 
  |`--from-file=<file>`
  |Specifies a single file that will be the only file in the build source. The
  file is placed in the root of an empty directory with the same file name.
  
  |`--from-repo=<local_source_repo>`
  |Specifies a path to a local repository to use as the binary input for a build.
  
negative.code: optional Dockerfile may be specified to override any Dockerfile in the build
  context. For `*Source*` builds, this is assumed to be an archive as described
  above. For `*Source*` and `*Docker*` builds, if `*binary.asFile*` is set the
  build context will consist of a single file named by the value of `*binary.asFile*`. 
  The `*contextDir*` field may be used when an archive is provided. Custom builds will 
  receive this binary as input on standard input (`stdin`).
  
  A binary source potentially extracts content (if `*asFile*` is not set), in which case `*contextDir*`
  allows changing to a subdirectory within the content before the build executes.
  
  The source definition is part of the `*spec*` section in the `*BuildConfig*`:
  