How to make a 'resource' template to get its manifest from a hard-wired Git input artifact?

[Stolz]

My goal is to submit a workflow whose YAML manifest is in a remote Git repository.

Of course I could reinvent the wheel and use multiple steps with custom 'container' templates (one to clone the repo, another to submit the fetched workflow manifest), but to keep things lean instead I would like to leverage Argo Workflows built-in features as much as possible. Namely:

• the hardwired Git artifacts feature and
• the Manifest From Artifact feature of the resource template.

However I cannot find any example of how to use both features combined. Reading the CRDs specs this is the best I've come up with to submit https://github.com/argoproj/argo-workflows/blob/main/examples/hello-world.yaml in a single step:

apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: submit-workflow-from-git-
  namespace: argo-workflows
spec:
  entrypoint: main
  arguments:
    parameters:
      - name: git-repository
        value: https://github.com/argoproj/argo-workflows.git
      - name: git-branch
        value: main
      - name: path-to-manifest-file
        value: examples/hello-world.yaml
  templates:
    - name: main
      inputs:
        artifacts:
          - name: cloned-repository
            path: /src
            git:
              repo: "{{workflow.parameters.git-repository}}"
              branch: "{{workflow.parameters.git-branch}}"
              singleBranch: true
              depth: 1
      resource:
        action: create
        manifestFrom:
          artifact:
            name: cloned-repository
            path: /src
            subPath: "{{workflow.parameters.path-to-manifest-file}}"

Unfortunately, the above config fails with read /src: is a directory error message.

So my question is, how can I make a 'resource' template to get its manifest from a hard-wired Git input artifact?

[static-moonlight]

In case you use a kustomization.yaml, you could do something like this:

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
[...]
resources:
  - git@gitlab.company.com:path/to/project.git/path/to/resource?ref=master

I use this mechanic in several workflow projects. I'm not 100% sure though, that this is what you wanted.