[x] I've searched the issue queue to verify this is not a duplicate feature request.
[x] I've pasted the output of kargo version, if applicable.
[x] I've pasted logs, if applicable.
Proposed Feature
Promotion steps/options which provide a possibility to use ArgoCD clusters metadata and propagate it as inputs (helm values in my case, but can also be a kustomization or something else) for rendering.
Motivation
I have infrastructure or environment specific variables (such as AWS account id or other ids) as ArgoCD cluster labels/annotations what provides me a possibility to propagate those labels/annotations as helm-values using ArgoCD applicationset and not hardcode those ids in manifests per environment/stage. I would like to manage those applications using Kargo with same degree of non-determinism
Suggested Implementation
Promotion step which provides a possibility to get ArgoCD clusters metadata to Kargo temporary workspace (which is used by Kargo for promotion). Probably it could be a generic (not Kargo specific) promotion step which could provide a possibility to get inputs from Kuberentes CRs from cluster managed by shard controller (or to get inputs from API)
Another promotion step which provides a possibility to render .yaml (in my case it could be values-something.yaml) file using inputs from Kargo workspace
Checklist
kargo version, if applicable.Proposed Feature
Promotion steps/options which provide a possibility to use ArgoCD clusters metadata and propagate it as inputs (helm values in my case, but can also be a kustomization or something else) for rendering.
Motivation
I have infrastructure or environment specific variables (such as AWS account id or other ids) as ArgoCD cluster labels/annotations what provides me a possibility to propagate those labels/annotations as helm-values using ArgoCD applicationset and not hardcode those ids in manifests per environment/stage. I would like to manage those applications using Kargo with same degree of non-determinism
Suggested Implementation