Push, Pull, Build, Bop Images

[zjrgov]

The changes made to support the Kaniko service workflow are very moderate on the runner side, and mostly depend on the user doing some ugly stuff in their job. I figure we'll want to abstract some of this away for them at some point, but it probably makes more sense to do that after / during a rewrite (see #25 for details and a walkthrough of the script steps).

package image:
  stage: package
  image: cloudfoundry/cli:8.7.10
  services:
    - name: gcr.io/kaniko-project/executor:debug
      alias: kaniko
      entrypoint: ["/busybox/sh"]
  script:
    - cf api https://api.fr.cloud.gov
    - cf auth $CLOUD_GOV_USER $CLOUD_GOV_PASS
    - cf target -o gsa-tts-devtools-prototyping -s zjr-gl-test
    - tar -C $CI_PROJECT_DIR -czf bundle.tar.gz .
    - ci_auth=$(echo -n $CI_REGISTRY_USER:$CI_REGISTRY_PASSWORD | base64)
    - >-
      kaniko_cfg="{\"auths\": {\"${CI_REGISTRY}\": {\"auth\": \"${ci_auth}\"}}}"
    - >-
      echo $kaniko_cfg |
      cf ssh "${SERVICE_PREFIX}kaniko" --command
      "/busybox/cat > /kaniko/.docker/config.json"
    - >-
      cat bundle.tar.gz |
      cf ssh "${SERVICE_PREFIX}kaniko" --command
      "/kaniko/executor --context tar://stdin --destination=$APP_IMAGE_TAG"

Closes #16
Closes #17
Closes #21
Closes #22

[pauldoomgov]

Good job getting this over the line!

[pauldoomgov]

praise: Painful but pragmatic! (Which is probably the rightful title of a Bash book.)

[pauldoomgov]

thought: The default is arbitrary - Worth adjusting if we find it is too little in many more cases.