[FEATURE REQ] Referring api specification by specifying its directory path

[cmergenthaler]

Please describe the feature.

Let's say we want to have one specification.yaml for both the API provisioning and for code generating, it would be nice to be able to reference to a specific path rather than expecting a specification.yaml in the apis folder.
A possible folder structure could look like this:

artifacts
  apis
    apiA
      apiInformation.json
    apiB
      apiInformation.json
src
  specification.yaml

Inside the apiInformation.json we would be able to use the api-spec /src/specification.yaml

[github-actions]

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

[waelkdouh]

@guythetechie is this something we can consider down the line?

[guythetechie]

@cmergenthaler - thanks for the suggestion. I'm reluctant to start parameterizing the path of certain artifact files, as this will increase the code complexity. It's the first time we've had this ask, and if it's a big enough concern, we can certainly revisit it.

In the meantime, I would suggest handling this in your CI/CD pipeline. Simply add a step to copy the specification file from src/specification.yaml to apis/apiA/specification.yaml prior to the step that runs the publisher.

We've envisioned the extractor/publisher exes to be fairly opinionated about how they handle things. The starter pipelines, on the other hand, can be easily customized to handle specific needs.