CLI doesn't support using external-configuration-api

[MeurillonGuillaume]

Component

cli

Describe the bug

The woodpecker-cli exec command fails when a repository uses an external configuration service instead of local configuration files. The error returned is

FTL error running cli error="could not detect pipeline config"

Steps to reproduce

1. Configure an external configuration service for the server (https://woodpecker-ci.org/docs/administration/configuration/server#configuration)
2. Register a repository in Woodpecker
3. Run a Pipeline
4. Download the build metadata.json
5. Login to the Server using the woodpecker-cli
6. Run woodpecker-cli exec --metadata-file metadata.json

Expected behavior

The CLI makes a call to the external configuration API to fetch the Workflow configuration or the Workflow configuration is stored in the build metadata, allowing debug builds to execute the exact same logic.

System Info

Woodpecker: 3.11.0
Kubernetes: v1.33.5

Additional context

No response

Validations

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/versions]