oc new-app/oc new-build parameter for not auto triggering build process: oc new-(app|build) --suppress-build

Problem description

When running oc new-app or oc new-build, this automatically triggers a build creation.
Especially Quarkus (and golang) tooling makes patching the BuildConfig necessary, see https://github.com/quarkusio/quarkus/blob/master/docs/src/main/asciidoc/openshift-s2i-guide.adoc

Both waiting for the first build to fail (could take 15 mins or more) or combining oc create ... with && oc cancel-build (can fail if build hasn't started yet) aren't really useful approaches.

In the spirit of the abandoned https://github.com/openshift/origin/issues/15429, I suggest adding a parameter

--suppress-build

that just cancels the first build execution.

Alternatively, the documentation could be enhanced in a way that shows how to patch the build config with the create commands (if possible).

Version

v3.11

Steps To Reproduce

1. Run e.g.

oc new-app quay.io/quarkus/centos-quarkus-native-s2i~{quickstarts-clone-url} --context-dir=getting-started --name=quarkus-quickstart-native

2. Try to do this w/o triggering the build creation.

Current Result

You cannot prevent OCP from building.

Expected Result

You can disable the build trigger with a parameter.

Especially for a good Quarkus adoption this is IMHO a crucial topic.

Start at the oc new-app and oc new-build command entry points and trace where the initial build is triggered. Check how both commands handle shared parameters; done means --suppress-build prevents that first build while preserving normal behavior when the flag is absent.