Are sync-wave only available for applications/app-of-apps?

[ruant]

I've re-read the docs a couple of times and tried my luck with google too but I can't get this to work for all manifest files.
So my question is, are sync-wave only available for applications/app-of-apps?
I have a working app-of-apps setup that actually does sync in the correct order, so it at least works for the app-of-apps approach.
How ever, in one of the "sub apps", i also need the manifests applied in a certain order, but this isn't happening.

So my thought right now is that sync-wave only applies to app-of-apps? And not all manifest files.
If that's the case, why this limitation? Why can't we have it applied to all manifest files?

How I have it set up now:

• App of apps, that's "boostrapping" my entire cluster with all needed "stuff", monitoring, metallb, kyverno, ingress controller, etc.
  This is getting applied in the specified order (more or less at least, some apps get's a healthy status before it should be, but that isn't really a problem since ArgoCD is awesome and retries a couple of times before giving up)
• Now let's take the first app that should be applied, MetalLB. Inside this "app" i have 3 manifests that should be applied.
  1. ArgoCD application using helm to install MetalLB (and it's CRDs)
  2. An IPAddressPool manfiest file defining an pool of IP's to use for External-IP's.
  3. An L2Advertisement manifest file that defines the pool name from step 2 to be announced.
• I've given them the following sync-wave numbers:
  1. 10
  2. 20
  3. 21
     Applied like this:

metadata:
  annotations:
    argocd.argoproj.io/sync-wave: "10"

But this part isn't working. ArgoCD is trying to apply the IPAddressPool and L2Advertisement manifest files first, which fails since the CRD's isn't created yet since the Application that is installing MetalLB isn't being tried at all.

[ruant]

My bad.
Didn't know ArgoCD did a "DryRun" before applying stuff, so since the two second manifest files both used a CRD that didn't exists yet ArgoCD didn't start applying any of the 3 manifest files.

To solve this I had to add the following to the two manifest files that used "unknown" CRDS.
This way ArgoCD skips the DryRun for these two files, and the sync order actually works as planned.

metadata:
  annotations:
    argocd.argoproj.io/sync-options: SkipDryRunOnMissingResource=true