Environment:

• OpenShift: Running in a private network
• Client Tools:
  • tkn version: 0.40.0
  • tkn-pac version: 0.33.0
  • oc version: 4.17.16
  • Server Version: 4.18.9
  • Pipelines version: 0.68.0
  • Triggers version: 0.31.0
  • Chains version: v0.24.0
  • Operator version: v0.75.0

Steps to Reproduce:

I ran the following command:

tkn-pac bootstrap --force-gosmee

During the process, it still detected an OpenShift route and prompted me:

👀 I have detected an OpenShift Route on: https://pipelines-as-code-controller-openshift-pipelines.apps.bruhl.ocp.vslen
? Do you want me to use it? No

Even though I specified --force-gosmee, it didn't seem to take effect—the CLI still detected and tried to use the OpenShift route.

Expected Behavior:

Using the --force-gosmee flag should skip OpenShift route detection and force the use of a gosmee proxy for GitHub webhook forwarding.

Actual Behavior:

Despite passing the --force-gosmee flag, the CLI still attempts to detect and prompt for an OpenShift route.

Additional Context:

I'm working in a restricted/private network where direct webhook access from GitHub is not possible. I want to use gosmee as the tunneling service to relay webhooks from GitHub.