anchor.diff:  is not specified, OpenShift will perform the following logic for retrieving the
   image:
   
  -1. If the image's tag is `latest`, OpenShift will always pull down the image from its registry
  -2. If the image's tag is not `latest`, and the image exists on the node, OpenShift will run the existing image
  -3. If the image's tag is not `latest`, and the image does not exist on the node, OpenShift will pull down the image from its registry
  +1. If the image's tag is `latest`, OpenShift will always pull down the image from its registry.
  +2. If the image's tag is not `latest`, and the image exists on the node, OpenShift will run the existing image.
  +3. If the image's tag is not `latest`, and the image does not exist on the node, OpenShift will pull down the image from its registry.
   
   If the pull policy is set to `PullIfNotPresent`, OpenShift will pull the image
   if it doesn't exist on the node.
  
positive.code: An Identity can only map to a single User, so logging in as a particular
  identity unambiguously determines the User.
  
  A User can have multiple Identities mapped to it. Multiple login methods can
  identify the same User.
  
  Sample UserIdentityMapping:
  
  
negative.code: }
  ----
  
  <1> `name` represents  the token name, used as an authorization code to exchange
  for an OAuthAccessToken.
  <2> The `clientName` value is the OAuthClient that requested this token.
  <3> The `expiresIn` value is the expiration in seconds from the
  creationTimestamp.
  <4> The `redirectURI` value is the location where the user was redirected to
  during the authorization flow that resulted in this token.
  <5> `userName` represents the name of the User this token allows obtaining an
  OAuthAccessToken for.
  <6> `userUID` represents the UID of the User this token allows obtaining an
  OAuthAccessToken for.
  ====
  
  === OAuthAccessToken
  