anchor.diff:  that it would not normally have access to, such as private repositories or
   repositories with self-signed or untrusted SSL certificates.
   
  -The following source secret configurations are supported:
  +The following source secret configurations are supported.  Follow the link to
  +learn how to create a source secret of the given configuration.
   
   - xref:gitconfig-file[Gitconfig File]
   - xref:basic-authentication[Basic Authentication]
  
positive.code: to meet your specific needs.
  ====
  
  All source secrets must be linked to the builder account and added to the build
  configuration using the following instructions:
  
  . Add the secret to the builder service account. Each build is run with
  the *builder* role, so you must give it access to your secret with the
  following command:
  +
  ====
  ----
  $ oc secrets link builder basicsecret
  ----
  ====
  
  . Add a `sourceSecret` field to the `source` section inside the `BuildConfig` and
  set it to the name of the `secret` that you created (`basicsecret`, in this
  example).
  +
  ====
  [source,yaml]
  ----
  
negative.code: 
  [NOTE]
  ====
  You can also use the `oc set build-secret` command to set the source secret on
  an existing build configuration:
  ----
  $ oc set build-secret --source bc/sample-build basicsecret
  ----
  ====
  
  xref:using-secrets-in-the-buildconfig[Defining Secrets in the
  BuildConfig] provides more information on this topic.
  
  