Indeed, I don’t understand why but although I went like 10 times on this page but somehow did not get what it was saying … I think I understood the “builtin” part of “Codefresh will use a built-in install/upgrade pipeline for performing the promotion” as “it will use the default pipeline that you can’t inspect”. Anyway, thanks for the pointer.
Although since I asked, I found a solution and the simple builtin pipeline was not sufficient to mimic the default behaviour, I had to add a bunch of environment stuff around. Documented values are indeed provided, but they’re not picked up by the default install/upgrade step.
I was not asking about secrets, but suggestions on where to store helm values files. As codefresh provides opinions on where to store charts (aka chartmuseum), and have opinions about “stages” (the helm kanban) I thought maybe there are ideas about where to store environment value files that depends on kanban columns (values-prod.yaml, values-staging.yaml …). I guess I’ll use a versioned S3 bucket or even a git repo, then.