"pepr build --custom-image / --registry-info" appears to honor only "--registry-info"

[btlghrants]

Background

While working #1654 I discovered that when trying to set both the --custom-image and --registry-info flags, the resulting image string only reflected the content of the --registry-info flag; the content of the --custom-image option was nowhere to be found.

Is this expected behavior? I couldn't find any reference to it in the pepr build docs, so... maybe it lives somewhere else?

Suggest that this be investigated. Current behavior codified in (upcoming) integration test for the pepr build cli:

• /integration/cli/build.registryinfo.test.ts : build > builds a module > using a custom registry > builds

DOD:

• Adds examples to cli npx pepr build --help output for custom-image and registry-info options
• Update the docs to show example results
• Throw a build error when both flags are used

Definition of Done

1. figure out whether this is a "real" error or just a matter of test setup / config, and
2. fix the error (if it is one), or
3. add a note to the pepr build output / docs stating which flags are non-collaborative.

[cmwylie19]

I believe this is intended, registryInfo if for creating a custom WASM image with a well defined name image = ${opts.registryInfo}/custom-pepr-controller:${cfg.pepr.peprVersion}`;. Custom image, it would then attempt to build the docker image.

-i, --custom-image, is just for setting a custom image in the deployments. like pepr:dev for example.