Skip to content

Better way to process CF_DOCKER_PASSWORD when pushing apps

Story

As a DevTools engineer, I would like to push apps with contextual registry credentials, So that I can provision jobs and services in parallel.

The CF Go library provides op.Push, a Go-based mirror of the cf push CLI command. This process expects the password for private registries to be "passed" as an environment variable—the same way the CLI works. This will probably get a little bit weird if we try to parallelize pushing services & job runners.

This relates to #23, and perhaps in part to #67.

Solution

A couple different solutions to this come to mind:

  1. Push a change upstream to have the Push op read from the ctx context that's right there, falling back to the env var if provided.
  2. Recreate the "push" process in our CF client adapter, as documented in the wiki.

Acceptance Criteria

Can push multiple job/service "apps" at once, each with images in different private registries.