Config Map as an Application source

[awilcots]

Would it be a good idea to add different config sources, other than git/help repository? Off of the top of my head, I'm thinking a config map source would be nice. A config map doesn't offer versioning or tracking, which I could understand as something to stray away from, as a history of changes would not be tracked. However, I feel like that should be a decision the consumer is able to make.

In my specific situation, I have argo workflows creating some k8s resources. The created resources I'd like to then be watched/managed by argocd. The resources created shouldn't change often, if at all. In this, I think involving github/helm as a point of failure is unnecessary, as well as the bloat logic to create either of those is undesirable. Alternatively, I could be able to drop the manifests in a config map, as either a single object inside a singe data item or each manifest could have it's own data field. Given that argocd can accept a git repo that just points to a series of manifests, and that's accepted, I wouldn't believe that this would be much of a mental stretch.

I'm curious as to know why this could be a bad idea, or something that the argo project wouldn't want to implement. I've come across this conversation that's in the relm of what I'm talking about, but it's not quite the same I don't believe.