Consider a workflow referencing a spec file in one of the functions:

      "name": "multiplication",
      "operation": "specs/multiplication.yaml#doOperation"

The required configuration options need to be defined as:

quarkus.rest-client.multiplication_yaml.url=http://localhost:8282
quarkus.openapi-generator.multiplication_yaml.auth.basic_auth.username=admin
...

If these properties are missing or incorrect, the user should be informed about it.

Currently, no message is logged and at runtime the http call will be made to localhost:80 and fails with a Connection refused (or similar) error, making it difficult to understand what is missing.