variable substitution promotion step

[jdolce]

I am wondering if there has been any thought on a promotion step that preforms variable substitution?

My team currently makes use of Flux's Kustomization Post Build Variable Substitution, and was hoping we could achieve something similar in Kargo.

sqsQueue: arn:aws:sqs:${aws_region}:${aws_accound_id}:MyQueue

Our Helm Chart values files might look something like the above, which then gets substituted based on environment. This approach allows us to have a single source of truth for environment config and allows application teams to define their config 1 time. Standardizing these variables inside of Helm Charts would be quite difficult as we use lots of 3rd party and internal charts.

We are in the early stages of migrating to Kargo and the rendered manifest pattern and having something like this would greatly speed up adoption.