anchor.diff:  
   All you have to do is to configure the generated image as an external artifact. You can find the steps to do that here.
   
  -So there you go. I hope you find it useful. If you have any questions, please feel free to comment and I’ll answer from whatever I’ve learnt so far.
  +So there you go. I hope you find it useful. If you have any questions, please feel free to comment and I'll answer from whatever I've learnt so far.
   
  
positive.code: 
  *While exploring how to do it, we had to spend some time to find out all the information we needed just to install and configure GoCD without the migration. So I decided to write this and a few other posts hoping someone like me would find it helpful. This is the second part on Configuring Google Container Registry (GCR) as an Artifact Store in GoCD. You can find the first part on [Installing and Configuring GoCD on GKE using Helm](https://www.gocd.org/2019/05/14/installing-configuring-gocd-gke-using-helm/).*
  
  GoCD allows configuration of artifact stores such as Dockerhub, Amazon’s ECR, Google’s GCR to store and pull docker image artifacts. Depending on your version you can get two types of configuration windows. Let me show the latest configuration window of the artifact store`
  
  INSERT IMAGE HERE
  
  There are two options based on the Registry Type. The first one is Amazon ECR. There are corresponding options for ECR Registry ID, AWS Region, AWS Access Key Id and AWS Secret Access Key.The second one says ‘Others’ and lists Dockerhub, GCR and private. For Dockerhub there are fields for username and password along with Docker Registry URL.
  
  The older plugin version does not have a separate option for Amazon ECR. It just has the same fields for all stores
  
  
negative.code: 
  Now if you try to create a service account, you might get a json file with the following fields:
  
  ```json
  {
    "type": "service_account",
    "project_id": "<project-id>”,
    "private_key_id": "<private-key-id>",
    "private_key": "<private-key>”,
    "client_email": "<client-email>,
    "client_id": "<client-id>",
    "auth_uri": "<auth-uri>",
    "token_uri": "<token-uri>",
    "auth_provider_x509_cert_url": "<auth-provider-x509-cert-url>",
    "client_x509_cert_url": "<client-x509-cert-url>”
  }
  ```
  
  This json file contains the keys necessary for authenticating with GCR to push or pull docker images. Going through the GitHub repository for information regarding how we can use the service account credentials, we came across [this issue](https://github.com/gocd/docker-registry-artifact-plugin/issues/9#issuecomment-426709466) that had a comment on how to use the service account.
  
  