Currently, the manifest source options available in Harness are all git repositories (or a Harness file).

For our use-case, teams will be packaging their CF manifest files alongside their service assets inside each artifact.

Rather than "pre-processing" an artifact, as was supported in Harness first-gen in order to de-couple multiple artifacts packaged together, we are looking to package artifacts individually but with the manifest.yml file packaged alongside the other artifact assets.