u/dankoverride

Running app-of-apps on ArgoCD where root Applications generate their leaves via an ApplicationSet. Because each generated leaf is a real top-level Application, the Applications overview lists every leaf alongside the roots, and the handful of roots I actually navigate from get lost in the generated ones.

The per-app resource tree shows the root -> children hierarchy nicely, but I can't find an equivalent grouped/collapsed view across the whole Applications list. Curious how others manage this at scale: do you rely on labels + filters, separate AppProjects per root, the favorites toggle, or is there a view mode I'm overlooking? Trying to get a "show me the roots, expand on demand" experience rather than a flat wall of generated apps.

The API and SDK are clean packages I can pin and upgrade deliberately. But for semconv I still end up copying attribute keys and enum values out of the docs into constants, and re-checking them every time the spec moves, especially the newer gen_ai.* ones. Some languages have a semconv constants package, others lag, and the experimental conventions basically are not importable yet. How are you all handling the drift in practice: generate constants from the YAML yourselves, vendor them, or hardcode and hope the spec does not shift under you? Mostly curious how teams keep app code and the spec in sync without it becoming a chore.