Can you deploy all the targets of a .kluctl.yaml in a GitOps Controller and not a specific one?

[signed-log]

I have a queuing app https://github.com/abacf/kube-dep

This app can be deployed N time for N queues. I integrated it with kluctl, and I now need to deploy the GitOps controller

How I envision that, would be, a target per queue like this

targets:
  - name: ruby-prod
    context: prod
    args:
      environnment: prod
      queue_name: ruby
      base_domain: 192-168-1-205.nip.io
    images:
      - image: redis
        resultImage: redis:7.2.4
      - image: app
        resultImage: ghcr.io/abacf/sae503:2.1.2
      - image: oliver006/redis_exporter
        resultImage: oliver006/redis_exporter:v1.58.0
  - name: ruby-staging
    context: staging
    args:
      environnment: staging
      queue_name: ruby
      base_domain: 192-168-1-200.nip.io
    images:
      - image: redis
        resultImage: redis:7.2.4
      - image: app
        resultImage: ghcr.io/abacf/sae503:2.1.2
      - image: oliver006/redis_exporter
        resultImage: oliver006/redis_exporter:latest

However, seeing the docs, it seems I can't use that method to deploy the software using GitOps

Target specifies the kluctl target to deploy. If not specified, an empty target is used that has no name and no context. Use ‘TargetName’ and ‘Context’ to specify the name and context in that case.

I am willing to make a wrapper script to create/destroy GitOps Controllers, but I've wanted to make sure I don't miss a feature.

[codablock]

I'm not sure I understand your question. The same controller can deploy as many kluctl projects and/or targets as you like. Just use multiple KluctlDeployment objects, one per target.

[signed-log]

Ideally, I would want my targets to be auto-detected and bulk applied/deleted without crafting a deployment for each target

[codablock]

Ah now I understand. No this is not possible right now and not planned. You can however put the KluctlDeployment itself into another GitOps deployment and then use some templating to create multiple KluctlDeployments depending on whatever logic you want.